TestCafe v1.4.0 Released

This release introduces the capability to inject custom scripts into tested pages.

Enhancements

⚙ Inject Scripts Into Tested Pages (#1739)

TestCafe now allows you to inject scripts into pages visited during the tests. Use this feature to add helper functions, mock browser API or import modules.

To add client scripts to all tests, specify them in the command line, API or configuration file. Use the following options:

  • the --cs (--client-scripts) command line argument

    testcafe chrome test.js --client-scripts mockDate.js,assets/react-helpers.js

  • the runner.clientScripts API method

    runner.clientScripts('mockDate.js', 'scripts/react-helpers.js');

  • the clientScripts configuration file property

    {
    "clientScripts": ["mockDate.js", "scripts/react-helpers.js"]
}

If you need to add scripts to individual fixtures or tests, use the fixture.clientScripts and test.clientScripts methods in test code.

fixture `My fixture`
    .page `http://example.com`
    .clientScripts('mockDate.js', 'scripts/react-helpers.js');

test
    ('My test', async t => { /* ... */ })
    .clientScripts('mockDate.js', 'scripts/react-helpers.js');

TestCafe also allows you to inject scripts into specific pages.

fixture `My fixture`
    .clientScripts({
        page: 'https://myapp.com/page/',
        path: 'scripts/vue-helpers.js'
    });

This is helpful when you need to override the browser API on particular pages and use the default behavior everywhere else.

You can specify the scripts to inject as follows:

  • pass the path to a JavaScript file to inject its content:

    fixture `My fixture`
    .clientScripts({ path: 'assets/jquery.js' });

  • use the module name to inject a module:

    fixture `My fixture`
    .clientScripts({ module: 'async' });

    TestCafe searches for the module’s entry point with Node.js mechanisms and injects its content. Note that the browser must be able to execute this module.

  • pass the code you need to inject:

    fixture `My fixture`
    .clientScripts({ content: 'Geolocation.prototype.getCurrentPosition = () => new Positon(0, 0);' });

For more information, see Inject Scripts into Tested Pages.

Bug Fixes

  • The browser no longer displays 404 errors after the test submits a form (#3560
  • TestCafe can now download files when testing in headless mode (#3127)
  • TypeScript no longer throws an error when fixture or fixture.page uses a tag function (#4042)
  • The load event now correctly fires for cached images
  • TestCafe can now read resources from asar archives
  • Fixed a bug when testcafe-hammerhead event listeners were called twice