build(deps-dev): bump testcafe from 1.20.1 to 3.7.0

[dependabot]

Bumps testcafe from 1.20.1 to 3.7.0.

Release notes

Sourced from testcafe's releases.

v3.7.0

TestCafe v3.7.0 Released

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 declare Metadata as an interface.

// testcafe.global.d.ts
declare module "testcafe" {
	global {
		interface Metadata {
			manual?: boolean,
		}
	}
}

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

• CDP client tab creation causes a WebSocket connection closed error in Chrome v130 (#8286).
• An unhandled promise rejection occurs while launching sub-windows (#8258).
• Assertions that perform visibility checks fail despite elements being visible on the page (#8237).
• The t.getCurrentCDPSession method returns unknown (#8228).
• [Native Automation] Request hooks are applied to skipped tests (#8229).
• A WebSocket connection closed error occurs while running TestCafe in Chrome v127. The updated version includes the --disable-search-engine-choice-screen flag (#8240).
• A leaveElement method call causes an error when the prevElement object is removed from the DOM (#8264).

v3.7.0-rc.4

What's Changed

• fix: docker server-test run fail fixed by @​Bayheck in DevExpress/testcafe#8329

Full Changelog: DevExpress/testcafe@v3.7.0-rc.3...v3.7.0-rc.4

v3.7.0-rc.3

What's Changed

• update: publish jobs update by @​Bayheck in DevExpress/testcafe#8317
• fix: devtools package moved from dev to prod packages by @​Bayheck in DevExpress/testcafe#8327

Full Changelog: DevExpress/testcafe@v3.7.0-rc.2...v3.7.0-rc.3

... (truncated)

Changelog

Sourced from testcafe's changelog.

TestCafe v3.7.0 Released

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 declare Metadata as an interface.

// testcafe.global.d.ts
declare module "testcafe" {
	global {
		interface Metadata {
			manual?: boolean,
		}
	}
}

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

• CDP client tab creation causes a WebSocket connection closed error in Chrome v130 (#8286).
• An unhandled promise rejection occurs while launching sub-windows (#8258).
• Assertions that perform visibility checks fail despite elements being visible on the page (#8237).
• The t.getCurrentCDPSession method returns unknown (#8228).
• [Native Automation] Request hooks are applied to skipped tests (#8229).
• A WebSocket connection closed error occurs while running TestCafe in Chrome v127. The updated version includes the --disable-search-engine-choice-screen flag (#8240).
• A leaveElement method call causes an error when the prevElement object is removed from the DOM (#8264).

v3.6.2 (2024-07-02)

Bug Fixes

• [Native Automation] TestCafe incorrectly uploads files in Chrome v125 and up. (#8198)
• TestCafe dependencies include the vulnerable endpoint-utils package (#8207). The updated version includes the address package instead.

v3.6.1 (2024-06-10)

Bug Fixes

• TestCafe incorrectly calculates the dimensions of multi-line elements. (#8179)
• TestCafe incorrectly executes the resizeWindow method if you maximize the target window first. (#8157)

TestCafe v3.6.0 Released

... (truncated)

Commits

• 716aa91 release: v3.7.0 (#8334)
• d218487 fix: docker server-test run fail fixed (#8329)
• 2efbfda fix: devtools package moved from dev to prod packages (#8327)
• c516f7b update: publish jobs update (#8317)
• f3fe938 release: 3.7.0-rc.2 (#8316)
• f1bfeae fix: add --disable-component-extensions-with-background-pages flag to default...
• d5cb4db release: upd package-lock (#8302)
• 803ebb1 release: 3.7.0-rc.1 (#8301)
• 82a57ef fix: The 'WebSocket connection closed' error on Chrome 130 (#8297)
• 051ee10 build(deps-dev): bump rollup from 2.16.1 to 2.79.2 (#8291)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by kirovboris, a new releaser for testcafe since your current version.

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)