Skip to main content

Limitations for TestCafe

Special Characters in Test Names​

We recommend that you avoid using special characters when naming your tests. If your test name contains any special characters, your test may not run, or its artifacts may not be visible on our platform.

Chrome 130+​

TestCafe 3.6.2 and lower do not work with Chrome 130+. Disable native automation as a workaround.

Chrome/Edge + Sauce Connect​

When using Sauce-Connect, the browsers Chrome and Edge will not make use of the tunnel when browsing a website. They will behave as if there is no tunnel defined.

TestCafe Native Automation + Chrome + Sauce Connect​

If your tests are issuing TestCafe HTTP requests and require a Sauce Connect tunnel, you will need to either set the proxy manually or disable TestCafe's Native Automation.

Disable Native Automation​

This is the recommended approach, which poses less of a hassle. Disable Native Automation in your .testcaferc.js:

module.exports = {
  disableNativeAutomation: true,
};

and then ensure that our runner picks up the TestCafe config file by also specifying it in the saucectl yaml config:

testcafe:
  version: 3.4.0
  configFile: .testcaferc.js

Manually Setting the Request Proxy:​

Alternatively, you can apply the proxy settings as you make requests:

// HTTP_PROXY is pre-populated when using Sauce Connect
const items = process.env.HTTP_PROXY.split(':');
const host = items[1].replaceAll('/', '');
const port = items[2];
const response = await t.request({
  url: `http://some-internal-resource.example.com/`,
  method: 'get',
  proxy: {
    protocol: 'http',
    host,
    port,
  }
});