Skip to content

Commit

Permalink
Merge pull request #13 from dnotes/changeset-release/main
Browse files Browse the repository at this point in the history
chore: new release candidate
  • Loading branch information
dnotes authored Oct 30, 2024
2 parents 7f50c7d + 5de05c5 commit 5105448
Show file tree
Hide file tree
Showing 7 changed files with 79 additions and 47 deletions.
5 changes: 0 additions & 5 deletions .changeset/fluffy-spies-hang.md

This file was deleted.

35 changes: 0 additions & 35 deletions .changeset/tidy-bottles-fetch.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/wet-ears-perform.md

This file was deleted.

35 changes: 35 additions & 0 deletions packages/main/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,40 @@
# quickpickle

## 1.5.0

### Minor Changes

- 974e09d: ## Configuration of the world variable

QuickPickle now handles setting up the WorldConfig for any world builder
that extends the QuickPickleWorld class. That worldConfig is now accessable
in world.info.config.worldConfig, and in the read-only getter world.worldConfig.

The @quickpickle/playwright plugin has been updated to use the new API.

Any world builder classes using the old API will continue to function as before
for the time being.

## New API available for "soft" failure

Occasionally you may want to allow a scenario to continue running even after
a step has failed. Some use cases might be:

- to check the nature of the error thrown in a previous step
- to see all the errors from a longer list of steps
- to take a screenshot if there are any errors

There is now an API for this purpose: Scenarios can be tagged for "soft" failure.
The default tags are "@soft" or "@softfail", which can be configured at "softFailTags".
Scenarios tagged for soft failure will continue to run until the end of the Scenario,
and the Before and After hooks will be run as well. Any errors will be collected in
world.info.errors. If there are errors after the last step and After hooks have run,
then the Scenario will fail.

Note that this is analogous but slightly different from soft assertions in other
test frameworks like Vitest and Playwright, in that if you don't clear out the
accumulated errors, the Scenario will still fail at the end.

## 1.4.0

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/main/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "quickpickle",
"version": "1.4.0",
"version": "1.5.0",
"description": "Plugin for Vitest to run tests written in Gherkin Syntax.",
"keywords": [
"BDD",
Expand Down
42 changes: 42 additions & 0 deletions packages/playwright/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,47 @@
# @quickpickle/playwright

## 0.10.0

### Minor Changes

- 974e09d: ## Configuration of the world variable

QuickPickle now handles setting up the WorldConfig for any world builder
that extends the QuickPickleWorld class. That worldConfig is now accessable
in world.info.config.worldConfig, and in the read-only getter world.worldConfig.

The @quickpickle/playwright plugin has been updated to use the new API.

Any world builder classes using the old API will continue to function as before
for the time being.

## New API available for "soft" failure

Occasionally you may want to allow a scenario to continue running even after
a step has failed. Some use cases might be:

- to check the nature of the error thrown in a previous step
- to see all the errors from a longer list of steps
- to take a screenshot if there are any errors

There is now an API for this purpose: Scenarios can be tagged for "soft" failure.
The default tags are "@soft" or "@softfail", which can be configured at "softFailTags".
Scenarios tagged for soft failure will continue to run until the end of the Scenario,
and the Before and After hooks will be run as well. Any errors will be collected in
world.info.errors. If there are errors after the last step and After hooks have run,
then the Scenario will fail.

Note that this is analogous but slightly different from soft assertions in other
test frameworks like Vitest and Playwright, in that if you don't clear out the
accumulated errors, the Scenario will still fail at the end.

### Patch Changes

- 7f50c7d: added screenshots for elements, and fixed save location for visual regression tests
- 7fc2026: provide better error messages for metatag tests
- Updated dependencies [974e09d]
- [email protected]

## 0.9.9

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/playwright/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@quickpickle/playwright",
"version": "0.9.9",
"version": "0.10.0",
"description": "Support files for running tests with Playwright using QuickPickle (Gherkin in Vitest).",
"keywords": [
"BDD",
Expand Down

0 comments on commit 5105448

Please sign in to comment.