chore(deps): update dependency @badeball/cypress-cucumber-preprocessor to v23 #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^22.0.1
->^23.2.1
Release Notes
badeball/cypress-cucumber-preprocessor (@badeball/cypress-cucumber-preprocessor)
v23.2.1
Compare Source
v23.2.0
Compare Source
Add a flag to turn expectation errors soft. Relates to #1313 and #1222.
During creation of message reports, which the JSON & HTML reports are products of, some test state is tracked by this library. This requires taking into account a myriad of edge cases, mostly related to Cypress' reload behavior. There are however likely several remaining edge cases that are unaccounted for.
In case of #1222, the fail fast strategy adopted here appeared to mask an underlying issue. I suspect this might also be the case for #1313 and similar issues. Thus an option for erroring softly is introduced. With this option, instead of throwing fast in Cypress' event handlers, the preprocessor will emit an error message to stderr at the end of a run.
My hope is that this will make it easier for the end-user to provide proper reproducible examples when running into these errors. Additionally, it can be useful for users whom which reports aren't strictly a necessity but do encounter such errors.
This option can be configured similar to other options, with examples shown below.
v23.1.0
Compare Source
Bumb engine requirement to Node v20.
Expand type signature of scenario and step hooks, to allow tags to be defined using pure string arguments. This is in line with how cucumber-js behaves.
Add support for attachments with filenames. This is in line with how cucumber-js behaves.
Implement
log
, as seen in cucumber-js.Implement
link
, as seen in cucumber-js.Minor changes to the messages report, to ensure compatibility with
cucumber-js
.v23.0.0
Compare Source
Breaking changes:
Dropped support for Cypress v11.
Dropped support for Node v18.
Other changes:
v22.2.0
Compare Source
Add TypeScript support for custom world in hooks, fixes #1304.
Add an option to disable attaching screenshots to reports, fixes #1306.
true
, retaining existing behavior for other users.v22.1.0
Compare Source
Gracefully handle sourcemaps when running component tests with webpack and chunks enabled (default behavior), fixes #1296.
Avoid setting
sourcesContent: false
to esbuild when using theprettySourceMap
option, relates to #1285.This means that the default bundle when using
prettySourceMap
is larger and may affect performance. However, the in-app experience is likely more aligned with user expectation. Users can disable this behavior by explicitly configuringsourcesContent: false
themselves, as shown below.Configuration
📅 Schedule: Branch creation - "after 10pm every weekday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.