TestCafe v0.23.0 Release Notes
Release Date: 2018-10-25 // over 5 years ago-
โจ Enhancements
โ :gear: Stop Test Run After the First Test Fail (#1323)
๐ง You can now configure TestCafe to stop the entire test run after the first test fail. This saves your time when you fix problems with your tests one by one.
๐ Specify the --sf flag to enable this feature when you run tests from the command line.
testcafe chrome my-tests --sf
๐ In the API, use the stopOnFirstFail option.
runner.run({ stopOnFirstFail: true })
โ :gear: View the JavaScript Errors' Stack Traces in Reports (#2043)
๐ Now when a JavaScript error occurs on the tested webpage, the test run report includes a stack trace for this error (only if the --skip-js-errors option is disabled).
๐ [A report that contains a stack trace for a client JS error](docs/articles/images/client-error-stack-report.png)
โ :gear: Browsers are Automatically Restarted When They Stop Responding (#1815)
โ If a browser stops responding while it executes tests, TestCafe restarts the browser and reruns the current test in a new browser instance. โ If the same problem occurs with this test two more times, the test run finishes and an error is thrown.
๐ Bug Fixes
- โ An error message about an unawaited call to an async function is no longer displayed when an uncaught error occurs (#2557)
- โ A request hook is no longer added multiple times when a filter rule is used (#2650)
- โ
Screenshot links in test run reports now contain paths specified by the
--screenshot-pattern
option (#2726) - โ Assertion chains no longer produce unhandled promise rejections (#2852)
- โ
The
moment
loader now works correctly in the Jest environment (#2500) - โ TestCafe no longer hangs if the screenshot directory contains forbidden symbols (#681)
- โ
The
--ssl
option's parameters are now parsed correctly (#2924) - โ TestCafe now throws a meaningful error if an assertion method is missing (#1063)
- โ TestCafe no longer hangs when it clicks a custom element (#2861)
- โ TestCafe now performs keyboard navigation between radio buttons/groups in a way that matches the native browser behavior (#2067, #2045)
- โ
The
fetch
method can now be used with data URLs (#2865) - โ
The
switchToIframe
function no longer throws an error (#2956) - โ TestCafe can now scroll through fixed elements when the action has custom offsets (#2978)
- โ You can now specify the current directory or its parent directories as the base path to store screenshots (#2975)
- โ Tests no longer hang up when you try to debug in headless browsers (#2846)
- ๐ The
removeEventListener
function now works correctly when an object is passed as its third argument (testcafe-hammerhead/#1737) - โ
Hammerhead no longer adds the
event
property to a nullcontentWindow
in IE11 (testcafe-hammerhead/#1684) - โ The browser no longer resets connection with the server for no reason (testcafe-hammerhead/#1647)
- โ Hammerhead now stringifies values correctly before outputting them to the console (testcafe-hammerhead/#1750)
- โ A document fragment from the top window can now be correctly appended to an iframe (testcafe-hammerhead/#912)
- โ
Lifecycle callbacks that result from the
document.registerElement
method are no longer called twice (testcafe-hammerhead/#695)