TestCafe 为现代web开发堆栈提供自动化的跨浏览器测试

v1.4.1 (2019-8-15)

Bug Fixes

• Drag now works correctly in Chrome Mobile on Android and Chrome device emulator with touch screens (#3948)
• Live Mode no longer fails when it restarts tests that import other modules on Node.js v12 (#4052)
• TestCafe now types into inputs wrapped in label elements correctly (#4068)
• test.clientScripts no longer override fixture.clientScripts (#4122)

v1.4.0 (2019-8-7)

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-hammerhead/#1959)
• TestCafe can now read resources from asar archives (testcafe-hammerhead/#2033)
• Fixed a bug when testcafe-hammerhead event listeners were called twice (testcafe-hammerhead/#2062)

v1.3.3 (2019-7-17)

Bug Fixes

• TestCafe now throws an error if the specified TypeScript configuration file does not exist (#3991)
• TypeScript compilation time has been reduced for a large number of files (#4010)
• Expressions with the += operator are now expanded only when required (testcafe-hammerhead/#2029)
• Parentheses around the await expression are now preserved in the processed scripts (testcafe-hammerhead/#2072)
• Fixed a compatibility issue with Firefox 68 that prevented text selection (testcafe-hammerhead/#2071)

v1.3.2 (2019-7-11)

⚙️ Package dependencies have been upgraded to avoid CVEs found in the 'lodash' package

Bug Fixes

• TestCafe no longer hangs when a disconnected browser reconnects to the network (#3929)

v1.3.1 (2019-7-5)

This release fixes an issue caused by tsconfig.json auto-detection.

Breaking Changes

💥 TypeScript Configuration File Location is Required to Apply the Custom Compiler Settings (#3983)

Version 1.3.0 introduced support for custom TypeScript configuration files where you can provide the compiler options. This feature included automatic detection of these configuration files. If the directory from which you run tests contained a tsconfig.json file, TestCafe would apply it by default.

However, this behavior caused troubles for users who have already had tsconfig.json files with conflicting settings in their projects. TestCafe attempted to apply these configurations, which resulted in issues with test compilation.

In v1.3.1, we have disabled tsconfig.json auto-detection. Now you must explicitly specify the tsconfig.json file location to apply the compiler settings. You can do it in one of the following ways:

• the --ts-config-path command line parameter,

  testcafe chrome my-tests --ts-config-path /Users/s.johnson/testcafe/tsconfig.json

• the runner.tsConfigPath API method,

  runner.tsConfigPath('/Users/s.johnson/testcafe/tsconfig.json');

• the tsConfigPath configuration file property.

  {
      "tsConfigPath": "/Users/s.johnson/testcafe/tsconfig.json"
  }

We strongly recommend that you upgrade to v1.3.1. We apologize for any inconvenience.

v1.2.1 (2019-6-10)

Bug Fixes

• Fixed a Chrome 75 compatibility issue when t.typeText typed each character at the beginning of the input (#3865)
• Fixed a bug when a test with an unhandled promise rejection passed (#3787)
• The native dialog handler is now applied when a role redirects to the login page (#2969)

v1.2.0 (2019-5-28)

Enhancements

⚙️ Custom Reporters Can Now Handle Test Start (#3715) by @Ivan-Katovich

We have added an optional reportTestStart method to reporter API. This method fires each time a test starts. You can override it to output information about the started test:

async reportTestStart (name, meta) {
    this.write(`Starting test: ${name} (${meta.severity})`)
        .newline();
}

This method also enables better integration with third-party reporter frameworks. For instance, allure requires that you perform some actions (namely, specify the test steps) before a test starts. Now you can do this in the reportTestStart method in a custom reporter.

See the reportTestStart method description in Reporter Methods.

Bug Fixes

• Fixed a regression that prevented non-responsive browsers from restarting (#3781)
• Fixed an issue when t.click triggered the click event twice (#3645)
• Fixed a regression that prevented TestCafe from checking checkbox inputs with t.click (#3482)
• TestCafe TypeScript definitions no longer cause the Cannot find namespace 'NodeJS' error (#3719)
• TestCafe no longer removes the Authorization header when Fetch API is used (testcafe-hammerhead/#2020)
• TestCafe now provides correct values for the form.elements.length property (testcafe-hammerhead/#2009)
• Fixed the Invariant Violation React error caused by TestCafe Hammerhead (testcafe-hammerhead/#2000)
• Fixed a regression that disabled the IE=edge meta tag (testcafe-hammerhead/#1963)
• Fixed an issue that prevented t.setFilesToUpload from raising the change event on some file inputs (testcafe-hammerhead/#2007)