v2.5.0-rc.3

What's Changed

• nativeAutomation: fix typings by @Artem-Babich in #7612

Full Changelog: v2.5.0-rc.2...v2.5.0-rc.3

v2.5.0-rc.2

release: publish 2.5.0-rc.2

v2.5.0-rc.1

What’s Changed

• feat: add possibility to pass additional data to the reporter plugin (closes #3584) (#7562) @Artem-Babich
• Set hostname to 'locahost' if the proxyless mode is enabled to prevent block-mixed-content error (closes #7595) (#7596) @AlexKamaev
• fix lodash type errors (#7594) @Artem-Babich
• feat: moved esm mode from experimental (#7574) @Aleksey28
• proxyless: make the 'experimental' option regular (#7583) @miherlosev
• test for do not modify authorization header in proxyless mode PR in hh (#7587) @AlexKamaev
• remove some skipped test in the proxyless mode, add comments (#7586) @AlexKamaev
• actualize proxyless tests (#7580) @AlexKamaev
• proxyless: move the 'experimentalProxyless' option from factory function to the runner. (#7565) @miherlosev
• actualize skipped tests in proxyless (#7578) @AlexKamaev
• correct which property emulation for cdp events (fix hover for DevExtreme) (#7564) @AlexKamaev
• proxyless: refactoring 2 (#7563) @miherlosev
• proxyless: refactoring (#7560) @miherlosev
• fix scroll position for cdp events (#7559) @AlexKamaev
• proxyless: mouse move automation (#7554) @AlexKamaev
• skip disablePageCaching tests in proxyless until multiple windows support (#7545) @Artem-Babich
• fix request API protocol in proxyless (#7556) @Artem-Babich
• refactor: optimized workflow actions (#7552) @Aleksey28

v2.4.0

v2.4.0 (2023-03-06)

TestCafe v2.4.0 introduces the Visual Selector Debugger. You can now create and debug Selector queries in the browser window.

Visual Selector Debugger

TestCafe v2.4.0 displays the Visual Selector Debugger panel when you activate Debug Mode. Use the panel to debug Selector queries from your test, or generate new Selector queries.

If a Selector query causes your test to fail, add the t.debug() command after the last successful action, and launch the test.

When the test reaches the breakpoint, the window that runs the test displays the Selector Debugger panel. Copy the failing Selector query from test code to the Selector Debugger input field.

• TestCafe highlights page elements that match the Selector query.
• If no elements match the Selector query, the panel displays the No Matching Elements warning.
• If your Selector query contians a syntax error, the panel displays the Invalid Selector warning.

To interactively generate a Selector query, click the Pick button, and select the target element on the page.

For more information on the panel, its capabilities, and limitations, read the Visual Selector Debugger Guide.

Bug Fixes

• TestCafe cannot execute the t.request action in proxyless mode (#7523).

v2.4.0-rc.1

What’s Changed

• [README] Remove the 2022 Feedback Survey banner (#7466) @titerman
• skip request timeout tests in proxyless until native timeout support is implemented (#7543) @Artem-Babich
• proxyless: correctly handle page with invalid certificate (#7542) @miherlosev
• README edits (#7541) @titerman
• proxyless: speed up 'pressKey' action (#7540) @miherlosev
• feat: Detect if TestCafe is being run on virtual machine (#7539) @Dmitry-Ostashev
• fix: live mode and support live mode with proxyless (#7528) @Artem-Babich
• proxyless: speed up 'typeText' action (#7536) @miherlosev
• fix: vulnerabilities in Jekyll dependencies (#7537) @kirovboris
• fix: add headed task to tasks queue (#7538) @Artem-Babich
• add a separate headed browsers task for tests that cannot be run in headless mode (#7530) @Artem-Babich
• fix: job reporting tests in proxyless (#7534) @Artem-Babich
• proxyless: implement 'typeText' action (#7525) @miherlosev
• Update LICENSE (#7527) @helen-dikareva
• proxyless: implement 'keyPress' action (#7499) @miherlosev
• fix(Selector Inspector): selectors parsing in experimental debug mode (#7517) @felis2803
• fix: raise reporter reportTaskDone event if browser has been disconnected (#7518) @Artem-Babich
• fix: support API testing in proxyless mode and attach cookies to the request with hammerhead (#7504) @Artem-Babich
• proxyless: fix browser reconnect tests (#7512) @AlexKamaev
• fix(Selector Inspector): selector is parsed correctly in life mode (#7516) @felis2803
• fix set caret position for the proxyless click command (#7505) @AlexKamaev
• feat: selector inspector panel (closes #7375) (#7372) @felis2803
• fix navigate to about:blank/file:// page in the CDP mode (#7498) @AlexKamaev
• test: turned of tests for internet explorer (#7508) @Aleksey28

v2.3.1

v2.3.1 (2023-02-09)

TestCafe v2.3.1 introduces a number of bug fixes.

Bug Fixes

• Client-side code with optional chaining may trigger a TestCafe error (#7387).
• TestCafe cannot interact with images from the Shadow DOM (#7454).
• TestCafe v2.3.0 fails to launch when the test.meta method precedes test code (#7482).
• When TestCafe launches a headless instance of Google Chrome in proxyless mode, it cannot interact with elements that are overlapped by the status bar (#7483).

v2.3.1-rc.2

What’s Changed

• release: bump version (2.3.1-rc.2) (#7503) @Aleksey28

v2.3.1-rc.1

What’s Changed

• release: publish 2.3.1-rc.1 (#7497) @Aleksey28
• try to fix the urlToHttpOptions issue in the TestCafe Studio (#7495) @AlexKamaev
• fix condition for internal requests in proxyless to allow downloading of the xml files (#7492) @AlexKamaev
• Handle unreachable pages + remove some tests from exceptions (#7490) @AlexKamaev
• fix: fixed regression with using tests and fixture methods (#7491) @Aleksey28
• proxyless: update test run glob (#7486) @miherlosev
• hide status bar when clicking using CDP (closes #7483) (#7484) @AlexKamaev
• release: publish 2.3.1-alpha.1 (#7487) @miherlosev
• proxyless: support client scripts (#7474) @miherlosev
• fix scenarios in proxyless mode if user code rewrites the bind method (#7480) @AlexKamaev
• Basic Http-auth in proxyless mode (#7476) @AlexKamaev
• fix: fixed click on SVG inside shadowRoot (#7458) @Aleksey28
• proxyless: perform 'click' using CDP (iframes support) (#7463) @miherlosev
• Proxyless context storage (#7467) @AlexKamaev

v2.3.1-alpha.1

What’s Changed

• release: publish 2.3.1-alpha.1 (#7487) @miherlosev
• proxyless: support client scripts (#7474) @miherlosev
• fix scenarios in proxyless mode if user code rewrites the bind method (#7480) @AlexKamaev
• Basic Http-auth in proxyless mode (#7476) @AlexKamaev
• fix: fixed click on SVG inside shadowRoot (#7458) @Aleksey28
• proxyless: perform 'click' using CDP (iframes support) (#7463) @miherlosev
• Proxyless context storage (#7467) @AlexKamaev

v2.3.0

v2.3.0 (2023-01-30)

TestCafe v2.3.0 introduces create-testcafe — an interactive tool that allows you to initialize a new TestCafe project in seconds. The update also includes experimental ECMAScript module support and a number of bug fixes.

IMPORTANT:
TestCafe v2.3.0 ends support for Node.js 14 due to a known vulnerability in the babel-plugin-module-resolver module.

Install an up-to-date version of the Node.js runtime to use TestCafe v2.3.0 and up.

The official maintenance period for Node.js 14 elapses on April 1st, 2023.

create-testcafe

Use the create-testcafe tool to initialize a new TestCafe project, or add TestCafe to an existing Node.js application.

Execute the following command to launch create-testcafe:

npx create-testcafe

The create-testcafe tool allows you to perform the following actions with a single command:

1. Create a new folder for the TestCafe project (optional).
2. Create a new local installation of TestCafe and its dependencies.
3. Create and initialize a TestCafe configuration file.
4. Create a separate subfolder for tests.
5. Populate the test folder with test examples (optional).
6. Create a YAML file with a GitLab Actions workflow that runs TestCafe tests (optional).

Read the TestCafe Setup Wizard guide for more information on the create-testcafe tool.

Experimental: ECMAScript module support

IMPORTANT:
ESM module suppport works with Node.js 16 and up.
TestCafe has always used CommonJS syntax for module imports:

const { x } = require('y');

An increasing number of Node.JS packages abandon CommonJS in favour of ECMAScript module syntax:

import {x} from 'y'

Enable the --experimental-esm CLI flag to import modules that do not support CommonJS. Note: tests with ECMASCript module syntax are subject to additional requirements.

testcafe chrome test.js --experimental-esm

Additional Reuqirements

To run tests with ECMAScript import statements, make sure that your project meets at least one of the following requirements:

1. The value of the type key in your project's package.json file is module.
2. The test files in your project use the .mjs extension.

Bug Fixes

• TestCafe doesn't delete expired cookies (#7432).
• TestCafe cannot handle windows that appear when the user clicks a link with a _blank target (#6926).
• TestCafe fails to start because it triggers the dns.setDefaultResultOrder method in older Node.js environments (#7447).
• TestCafe depends on a vulnerable, outdated version of the babel-plugin-module-resolver package (#7456).