TestCafe v1.5.0 Released

This release introduces the capability to disable page caching in TestCafe.


⚙ Page Caching Can be Disabled (#3780)

TestCafe may be unable to log in to the tested website correctly if the web server uses caching for authentication pages or pages to which users are redirected after login. See the User Roles topic for details.

If tests fail unexpectedly after authentication, disable page caching in TestCafe.

Use the fixture.disablePageCaching and test.disablePageCaching methods to disable caching during a particular fixture or test.

    .disablePageCaching `My fixture`
    .page `https://example.com`;
    ('My test', async t => { /* ... */ });

To disable page caching during the entire test run, use either of the following options:

  • the --disable-page-caching command line flag

    testcafe chrome my-tests --disable-page-caching
  • the disablePageCaching option in the runner.run method

    runner.run({ disablePageCaching: true });
  • the disablePageCaching configuration file property

        "disablePageCaching": true

If tests run correctly without page caching, we recommend that you adjust the server settings to disable caching for authentication pages and pages to which the server redirects from them.

Bug Fixes

  • Fixed an error that occured when a selector matched an <svg> element (#3684)
  • Fixed an issue when the reporter configuration file option was not applied (#4234)
  • Fixed a warning message about invalid tsconfig.json file (#4154)
  • LiveRunner.stop() now closes the browsers (#4107)
  • Quarantined tests now re-run correctly in live mode (#4093)
  • Fixed a bug when client scripts were not injected in live mode when it re-executed tests (#4183)
  • form.elements.length now returns the correct value for forms with file inputs
  • Fixed a bug when images were not displayed in inputs with the image type
  • Fixed an AngularJS compatibility issue that caused a TypeError
  • TestCafe now works correctly with servers that use JSZip to unpack uploaded files