chore(deps-dev): bump the npm_and_yarn group group with 1 update

[dependabot[bot]]

Bumps the npm_and_yarn group group with 1 update: testcafe.

Updates testcafe from 2.3.0 to 3.5.0

Release notes

Sourced from testcafe's releases.

v3.5.0 (2023-12-28)

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 https://github.com/DevExpress/testcafe/blob/HEAD[https://github.com/DevExpress/testcafe/blob/HEADthttps://github.com/DevExpress/testcafe/blob/HEAD.https://github.com/DevExpress/testcafe/blob/HEADdhttps://github.com/DevExpress/testcafe/blob/HEADehttps://github.com/DevExpress/testcafe/blob/HEADbhttps://github.com/DevExpress/testcafe/blob/HEADuhttps://github.com/DevExpress/testcafe/blob/HEADghttps://github.com/DevExpress/testcafe/blob/HEAD(https://github.com/DevExpress/testcafe/blob/HEAD)https://github.com/DevExpress/testcafe/blob/HEAD]https://github.com/DevExpress/testcafe/blob/HEAD(https://github.com/DevExpress/testcafe/blob/HEADxhttps://github.com/DevExpress/testcafe/blob/HEADrhttps://github.com/DevExpress/testcafe/blob/HEADehttps://github.com/DevExpress/testcafe/blob/HEADfhttps://github.com/DevExpress/testcafe/blob/HEAD:https://github.com/DevExpress/testcafe/blob/HEAD4https://github.com/DevExpress/testcafe/blob/HEAD0https://github.com/DevExpress/testcafe/blob/HEAD2https://github.com/DevExpress/testcafe/blob/HEAD7https://github.com/DevExpress/testcafe/blob/HEAD0https://github.com/DevExpress/testcafe/blob/HEAD7https://github.com/DevExpress/testcafe/blob/HEAD)https://github.com/DevExpress/testcafe/blob/HEAD method, TestCafe uses the query to populate the input field of the Visual Selector Debugger. The debugger highlights page elements that match the query.

t.debug(Selector('#header'));

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 the pathPattern property.

{
    "screenshots": {
        "pathPatternOnFails": "${DATE}_${TIME}/failedTests/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png"
    }
}

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:

t.takeScreenshot({
    pathPattern: "${DATE}_${TIME}/checkout-screenshot.png",
    fullPage: true
})

(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:

• Pop-up windows that launch file downloads.
• Browser window resizing.
• Screenshots.
• Video recording.

... (truncated)

Changelog

Sourced from testcafe's changelog.

v3.5.0 (2023-12-26)

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 https://github.com/DevExpress/testcafe/blob/master[https://github.com/DevExpress/testcafe/blob/masterthttps://github.com/DevExpress/testcafe/blob/master.https://github.com/DevExpress/testcafe/blob/masterdhttps://github.com/DevExpress/testcafe/blob/masterehttps://github.com/DevExpress/testcafe/blob/masterbhttps://github.com/DevExpress/testcafe/blob/masteruhttps://github.com/DevExpress/testcafe/blob/masterghttps://github.com/DevExpress/testcafe/blob/master(https://github.com/DevExpress/testcafe/blob/master)https://github.com/DevExpress/testcafe/blob/master]https://github.com/DevExpress/testcafe/blob/master(https://github.com/DevExpress/testcafe/blob/masterxhttps://github.com/DevExpress/testcafe/blob/masterrhttps://github.com/DevExpress/testcafe/blob/masterehttps://github.com/DevExpress/testcafe/blob/masterfhttps://github.com/DevExpress/testcafe/blob/master:https://github.com/DevExpress/testcafe/blob/master4https://github.com/DevExpress/testcafe/blob/master0https://github.com/DevExpress/testcafe/blob/master2https://github.com/DevExpress/testcafe/blob/master7https://github.com/DevExpress/testcafe/blob/master0https://github.com/DevExpress/testcafe/blob/master7https://github.com/DevExpress/testcafe/blob/master)https://github.com/DevExpress/testcafe/blob/master method, TestCafe uses the query to populate the input field of the Visual Selector Debugger. The debugger highlights page elements that match the query.

t.debug(Selector('#header'));

[!Video https://www.screencast.com/users/testcafe/folders/Default/media/4274d757-f7a4-4982-add4-43bb0ba35cff/embed]

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 the pathPattern property.

{
    "screenshots": {
        "pathPatternOnFails": "${DATE}_${TIME}/failedTests/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png"
    }
}

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:

t.takeScreenshot({
    pathPattern: "${DATE}_${TIME}/checkout-screenshot.png",
    fullPage: true
})

(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:

• Pop-up windows that launch file downloads.
• Browser window resizing.
• Screenshots.

... (truncated)

Commits

• 5cef9ac release: v3.5.0 (#8110)
• 1ae1198 release: v3.5.0-rc.1 (#8107)
• 51ad3bc feat: added pathPattern parameter to takeScreenshot method (#8093)
• c782239 add missing multiple-windows-na task (#8105)
• 61d6b4b feat: debug with selector option added (#8066)
• 51b54c7 feat: Added path-pattern-on-fails for screenshots (closes #7014) (#8055)
• 640cf6b feat: experimental multiple windows in native automation (#8080)
• c4d1c49 build: Set @​babel/plugin-transform-runtime to a 7.23.3 version (#8103)
• 20b6159 fix: In concurrent test run fixed awaiting of fixture before hook (#8097)
• 6cab394 build(deps): bump @​adobe/css-tools from 4.3.1 to 4.3.2 (#8096)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/TradeTrust/tradetrust-website/network/alerts).

[netlify[bot]]

✅ Deploy Preview for tradetrust-mainnet canceled.

Name	Link
🔨 Latest commit	a915a5e7ff738142d77fe8a5284882bf050db69d
🔍 Latest deploy log	https://app.netlify.com/sites/tradetrust-mainnet/deploys/65f17c741718cf00082f5cdd

[dependabot[bot]]

Looks like testcafe is up-to-date now, so this is no longer needed.