chore(deps): update dependency testcafe to v3.7.0 #1301
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:
3.4.0
->3.7.0
Release Notes
DevExpress/testcafe (testcafe)
v3.7.0
Compare Source
The TestCafe v3.7.0 update includes the capability to use
Metadata
as an interface,esm
configuration file option, and a number of bug fixes.meta-readmore
Declare Metadata Interface
Earlier versions of TestCafe supported
Metadata
as a type. In TestCafe v3.7.0 and higher, you should declareMetadata
as an interface.New Configuration File Option: esm
Earlier versions of TestCafe supported the ESM Module from the CLI only. In TestCafe v3.7.0 and higher, you can use the esm configuration file option. Note that this option only works with Node.js 18.19-18.xx, and 20.8.0 and up.
Bug Fixes
WebSocket connection closed
error in Chrome v130 (#8286).unknown
(#8228).WebSocket connection closed
error occurs while running TestCafe in Chrome v127. The updated version includes the--disable-search-engine-choice-screen
flag (#8240).leaveElement
method call causes an error when theprevElement
object is removed from the DOM (#8264).v3.6.2
Compare Source
Bug Fixes
v3.6.1
Compare Source
Bug Fixes
resizeWindow
method if you maximize the target window first. (#8157)v3.6.0
Compare Source
The TestCafe v3.6.0 update includes two minor changes and a number of bug fixes.
v3.5.0
Compare Source
TestCafe v3.5.0 includes multiple enhancements and bug fixes. Pass Selector queries to the Visual Selector Debugger, explore new ways to specify screenshot path patterns, and use a new experimental flag to run multi-window tests with native automation!
meta-readmore
Pass Selector queries to the Visual Selector Debugger
When you pass a Selector query to the t.debug() method, TestCafe uses the query to populate the input field of the Visual Selector Debugger. The debugger highlights page elements that match the query.
Use a custom path pattern for screenshots of failed tests
The
pathPatternOnFails
screenshot option allows TestCafe users to define a separate set of naming rules for screenshots taken on test failure. You can store these screenshots in a different folder, or add a common, recognizable element to their filenames. You can use this option on its own, or in conjunction with thepathPattern
property.Specify a path pattern for individual screenshots
Use the
pathPattern
option of the t.takeScreenshot action to specify a custom naming pattern for an individual screenshot:(Experimental) Run multi-window tests with native automation
TestCafe v2.5.0 was the first version of TestCafe to include native automation --- the capability to automate Chromium-based browsers with the native Chrome Debugging Protocol. This approach offers greater test stability and speed, but has a fair share of limitations. One of them is its incompatibility with multi-window tests.
TestCafe v3.5.0 offers an experimental solution for this issue --- the --experimental-multiple-windows CLI flag. If you enable this flag, you can run multi-window tests with the native automation engine.
The
--experimental-multiple-windows
mode does not support tests that include the following:Please do not use the
--experimental-multiple-windows
flag in production or for business-critical tasks.Bug Fixes
fixture.before
hook (#6999).Fixture.disableConcurrency
method does not disable concurrent test execution (8087).required
attribute (#8079).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.