Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency testcafe to v3.7.0 #1301

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 28, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
testcafe (source) 3.4.0 -> 3.7.0 age adoption passing confidence

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

Compare Source

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

Compare Source

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)

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.

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.
  • Video recording.

Please do not use the --experimental-multiple-windows flag in production or for business-critical tasks.

Bug Fixes
  • TypeScript compilation fails if project dependencies include '@​babel/plugin-transorm-runtime' v7.23.3 or greater (#​8091).
  • If you enable concurrent test execution, TestCafe launches tests before the conclusion of the fixture.before hook (#​6999).
  • The Fixture.disableConcurrency method does not disable concurrent test execution (8087).
  • TestCafe ignores the fullPage option when it takes screenshots on test failure (#​7761).
  • [Native Automation] TestCafe cannot populate file input fields with the required attribute (#​8079).
  • [Native Automation] TestCafe fails to execute tests that use service workers (#​8005, #​8054).
  • When an action target is obscured by a sticky element, TestCafe incorrectly calculates the scroll distance necessary to interact with the target. (#​7377).
  • Incorrect processing of front-end scripts causes automation errors (#​7713, #​8067, testcafe-hammerhead#2969).
  • TestCafe incorrectly processes failing network requests when it runs on Node.js v16 and greater (#​7097).
  • TestCafe incorrectly handles native dialogs in Mozilla Firefox (#​6815).

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from ea216a5 to 9936d2d Compare December 30, 2023 04:47
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from 1764844 to 987cb0e Compare January 9, 2024 03:28
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from 6ffab2f to 1f59469 Compare February 28, 2024 18:21
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from 5d74214 to 379dba0 Compare March 21, 2024 01:28
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from 07fe267 to f814819 Compare April 3, 2024 21:30
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 3 times, most recently from 76a1613 to 81d91cf Compare April 25, 2024 14:15
@renovate renovate bot changed the title chore(deps): update dependency testcafe to v3.5.0 chore(deps): update dependency testcafe to v3.6.0 Apr 25, 2024
@renovate renovate bot changed the title chore(deps): update dependency testcafe to v3.6.0 chore(deps): update dependency testcafe to v3.6.1 Jun 10, 2024
@renovate renovate bot changed the title chore(deps): update dependency testcafe to v3.6.1 chore(deps): update dependency testcafe to v3.6.2 Jul 3, 2024
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from 47fa76e to d93f4ad Compare August 18, 2024 13:27
@renovate renovate bot force-pushed the renovate/testcafe-3.x branch 2 times, most recently from 3d2d3e6 to 37aacbb Compare September 16, 2024 23:15
@renovate renovate bot changed the title chore(deps): update dependency testcafe to v3.6.2 chore(deps): update dependency testcafe to v3.7.0 Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants