Releases: dnotes/quickpickle
[email protected]
Patch Changes
-
2bb4509: Fixed several errors in rendering, including:
- `Backticks` and ${variables} were not escaped properly in Scenario Outlines
- Backslashes were not escaped properly in other strings
@quickpickle/[email protected]
Patch Changes
- Updated dependencies [2bb4509]
[email protected]
Patch Changes
-
db82746: Fixed problems with Scenario Outline rendering; under the following conditions,
and probably some others, the renderer would fail.- If a parameter were named "context"
- Any regex characters (e.g. *) in a parameter name
- Having a ton of examples
- If a parameter name started with a number
@quickpickle/[email protected]
Patch Changes
- Updated dependencies [db82746]
[email protected]
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.
Contributors
Assets 2
@quickpickle/[email protected]
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
Contributors
Assets 2
[email protected]
Minor Changes
- 4e4a90f: feat: add tags to test names for Vitest readouts
@quickpickle/[email protected]
Patch Changes
- Updated dependencies [4e4a90f]
[email protected]
Minor Changes
-
f350d15: - changed tagsMatch API for QuickPickleWorldInterface -- it now returns string[] or null,
which makes it easier for other plugins to get matching tags from a list.- added browser sizes to PlaywrightWorld; they can be chosen with tags or set via a Gherkin step.
-
94902af: feat: several additions to QuickPickleWorldInterface, fix explodeTags, refactor
feat: add QuickPickleWorld.toString() function that renders to a single descriptive line
feat: add QuickPickleWorld.info.stepIdx, to get the line number of the step within the scenario
feat: add QuickPickleWorld.info.explodedIdx, to get the index number for exploded tags
chore: renamed "qp" function to "gherkinStep", for better readability in traces
fix: fixed the explodeTags functionality when rendering
test: added tons of tests for the explodeTags functionality
@quickpickle/[email protected]
Patch Changes
-
f1167dc: fixed outcomes step definitions and tests for static HTML page
-
f350d15: - changed tagsMatch API for QuickPickleWorldInterface -- it now returns string[] or null,
which makes it easier for other plugins to get matching tags from a list.- added browser sizes to PlaywrightWorld; they can be chosen with tags or set via a Gherkin step.
-
07920cd: fixed all action step definitions, with tests
-
c85e2c0: Fixed file paths for default screenshots
-
Updated dependencies [f350d15]
-
Updated dependencies [94902af]