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:
^1.3.3
->^2.0.0
Release Notes
DevExpress/testcafe
v2.4.0
Compare Source
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.
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
v2.3.1
Compare Source
TestCafe v2.3.1 introduces a number of bug fixes.
Bug Fixes
test.meta
method precedes test code (#7482).v2.3.0
Compare Source
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.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
:The
create-testcafe
tool allows you to perform the following actions with a single command:Read the TestCafe Setup Wizard guide for more information on the create-testcafe tool.
Experimental: ECMAScript module support
TestCafe has always used CommonJS syntax for module imports:
An increasing number of Node.JS packages abandon CommonJS in favour of ECMAScript module syntax:
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.Additional Reuqirements
To run tests with ECMAScript
import
statements, make sure that your project meets at least one of the following requirements:type
key in your project's package.json file ismodule
..mjs
extension.Bug Fixes
_blank
target (#6926).dns.setDefaultResultOrder
method in older Node.js environments (#7447).babel-plugin-module-resolver
package (#7456).v2.2.0
Compare Source
TestCafe v2.2.0 introduces user-defined custom actions and an important experimental capability. Google Chrome users can now enable "proxyless mode" to speed up their test suite.
Custom Action Support
TestCafe users can now define custom test actions. Place the definition function in a JavaScript configuration file:
Include custom methods in your tests alongside other TestController methods.
Add the
customActions
prefix when you call the action:Experimental: Proxyless mode
TestCafe runs an under-the-hood reverse proxy to automate tests across different browsers. But this technique complicates the framework. Native automation protocols offer superior automation speeds and greater stability. That's why the TestCafe team decided to gradually phase the reverse proxy out in favor of native support for these automation protocols.
TestCafe v2.2.0 includes an experimental option that disables the proxy for Google Chrome.
You can enable this option in the command line interface, the Test Runner API, and the configuration file. Read the Proxyless mode guide for more information.
Bug Fixes
uuid
dependency (testcafe-reporter-dashboard#111)localhost
URL on Node.js v17 and up (#7396)importScript
function (#7378)Request
header when aniframe
points the user to a new URL (#7376, PR testcafe-hammerhead#2813 by @naggingant)<select>
element with themultiple
attribute (PR testcafe-hammerhead#2815)v2.1.0
Compare Source
Improvements
Improved handling of invisible elements
visibility: collapse
attribute.Improved handling of overlapped elements
Bug Fixes
Element.insertAdjacentText
method (#7352).v2.0.2
Compare Source
Bug Fixes
v2.0.1
Compare Source
Bug Fixes
EPIPE
errors that cause crashes (#7216).MaxListenersExceededWarning
warning (#7188).v2.0.0
Compare Source
TypeScript update
Read the TestCafe 2.0 Migration Guide to learn more.
Improvement: New ways to ignore JavaScript errors
TestCafe v2.0 introduces new ways to ignore JavaScript errors during test runs.
Two new methods allow you to ignore errors on a per-test or a per-fixture basis.
For each of the methods above, you can define the following options:
Read the Skip JavaScript Errors recipe to learn more.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.