v2.0.2

v2.0.2 (2022-10-31)

Bug Fixes

• TestCafe doesn't include the flags necessary to launch Chrome in a Podman container (PR #7307 by @timnederhoff)
• TestCafe doesn't warn users when it interacts with an element that obstructs the original action target (#2930)
• TestCafe incorrectly parses regular expressions passed to the --skip-js-errors CLI flag (#7301)

v2.0.1

v2.0.1 (2022-09-26)

Bug Fixes

• TestCafe yields incomplete video recordings in concurrency mode (#7218).
• Video recordings in concurrency mode yield EPIPE errors that cause crashes (#7216).
• Running TestCafe 1.20.1 and up with a high concurrency factor may nonetheless result in a MaxListenersExceededWarning warning (#7188).

v2.0.1-rc.1

What’s Changed

• release: get rid of pregenerated token (#7297) @AndreyBelym
• fix: getReportUrl method doesn't exist for testcafe-reporter-dashboard alpha version (#7290) @aleks-pro
• build: updated testcafe-browser-provider-browserstack (#7292) @Aleksey28
• fix: create correct raw-callsite for hooks (#7282) @Aleksey28

v2.0.1-alpha.2

What’s Changed

• fix: added creating screenshots even crop fails (#7267) @Aleksey28
• fix: downgrade testcafe reporter dashboard version (#7273) @aleks-pro
• proxyless: request error handling (part #1) (#7276) @miherlosev

v2.0.1-alpha.1

What’s Changed

• release: publish 2.0.1-alpha.1 (#7274) @miherlosev
• fix: forced stdin and stdout formats for ffmpeg (#7272) @Aleksey28
• fix warning for high concurrency level (closes #7188) (#7271) @miherlosev
• Add validation for skipJsErrors method argument options (#7270) @Artem-Babich
• fix video recording in concurrency mode (closes #7218) (#7268) @miherlosev
• fix: more tolerant error handling for errors raised into reporter plugin methods (#7260) @miherlosev

v2.0.0

v2.0.0 (2022-08-31)

TypeScript update

⚠️
TestCafe 2.0 includes a breaking change.
The framework’s built-in TypeScript compiler has been updated from version 3.9 to version 4.7. The vast majority of TestCafe users should not experience any issues during the upgrade. However, since TypeScript does not follow the semver versioning policy, even minor TypeScript updates contain breaking changes. Some TypeScript users may need to perform additional actions to ensure the compatibility of their test code.

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.

• Use the test.skipJsErrors method to ignore JavaScript errors in specific tests.
• Use the fixture.skipJsErrors method to ignore JavaScript errors for specific fixtures.
• The t.skipJsErrors action lets you ignore JavaScript errors at specific points in the test.

For each of the methods above, you can define the following options:

• The pageUrl option filters errors by page URL.
• The message option filters errors by message.
• The stack option filters errors by call stack.

Read the Skip JavaScript Errors recipe to learn more.

v2.0.0-rc.4

What’s Changed

• Fix skipJsErrors API, fix TS warnings (#7257) @Artem-Babich

v2.0.0-rc.3

What’s Changed

• fix: removed unnecessary disposing a temp directory for screenshots (#7250) @Aleksey28

v2.0.0-rc.2

What’s Changed

• release: publish 2.0.0-rc.2 (#7249) @miherlosev

v2.0.0-rc.1

What’s Changed

• release: publish 2.0.0-rc.1 (#7247) @miherlosev
• Add API for more flexible setting of "skip-js-error" option(closes #2775) (#7192) @Artem-Babich
• feat: Upgrade Typescript up to 4.x (#7103) @miherlosev
• test: SUBTITLES should contains defenitions of all test run phases (#7232) @felis2803