-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #13 from dnotes/changeset-release/main
chore: new release candidate
- Loading branch information
Showing
7 changed files
with
79 additions
and
47 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters