Fixed a bug when TestCafe Studio could not find a file to upload (T824527)
New Microsoft Edge Supported
TestCafe Studio can now record and run tests in the new Chromium-based Microsoft Edge on Windows and macOS. Select Microsoft Edge from the record or run configuration drop-down list. Headless mode is also supported for the new Edge.
Electron Version Updated
TestCafe Studio now uses Electron v7.1.2. This version provides stability and performance enhancements.
Linux 32-bit Support Discontinued
Recent Electron versions (v4 and newer) dropped support for the Linux 32-bit platform. Therefore, TestCafe Studio is no longer shipped for Linux 32-bit starting with v1.2.2.
macOS Application Notarized
The TestCafe Studio application for macOS passed through Apple notarization. This fixes compatibility issues with macOS 10.14.5+. TestCafe Studio no longer displays a warning that Apple cannot check it for malicious software. To run TestCafe Studio, applications from identified developers must be allowed in Preferences -> Security & Privacy -> General.
Status Panel Redesigned
The status panel displayed in the browser when tests are recorded and run has been redesigned to better fit into small browser windows and mobile devices.
This release includes the following bug fixes:
TestCafe Studio can now start if the PATH environment variable does not contain paths to system folders (T852021).
Fixed a bug when double click was not emulated with certain elements (T852023).
Remove the Selected Test Actions
The Remove actions button in the Test Editor toolbar now removes selected actions only. To remove all actions, use Cmd/Ctrl+A and click Remove actions.
Copy/Paste Behavior Enhancement
In the Explorer panel, you can now press Cmd/Ctrl+V when a test or hook is selected to paste the copied test/hook in the same fixture. Alternatively, you can select Paste from a test's context menu.
This release includes the following bug fixes:
Fixed a bug when TestCafe Studio could not start on Windows if registry editing is disabled (T835284)
Support for macOS 10.15 Catalina
TestCafe Studio is now compatible with macOS 10.15.
Custom Script Action
We added an action that executes custom TestCafe scripts in the recorded tests. You can use TestCafe API, third-party, and core Node.js modules in these scripts.
You can use features from any Node.js package to facilitate test scenarios where you need to communicate with external resources, access and process online or local data, etc.
Custom scripts allow you to create flexible test logic with conditional or iterative actions.
TestCafe Studio allows you to run custom scripts during recording to debug them. You can use the standard console output methods to print the debugging information.
If the tested webpage invokes a native browser dialog during the test scenario, you can check the dialog properties and specify how TestCafe should handle it (which button to click and what text to enter).
Use the new Handle Native Dialogs action to do this.
TestCafe Studio needs four vacant ports on the local machine to run and record tests. If you run tests on a remote device, TestCafe Studio will also need to know the hostname of the machine it's running on.
TestCafe Studio can automatically determine the hostname and choose vacant ports. However, depending on your network configuration, you may need to customize these settings. You can now do this in the Preferences/Settings dialog.
Faster and More Stable Tests with Intelligent Auto-Wait Mechanism
Automatically suspends test execution while waiting for element availability, page load completion, XHR requests, etc. The auto-wait mechanism also extends to assertions and thus stabilizes tests when you verify the page state. Customizable timeouts allow you to fine-tune built-in waiting mechanisms.
The Reports panel shows information on past test runs and current sessions that can be cancelled (if necessary).
A click on an item opens a detailed report on any given task. You can view test reports and export them into various formats (JSON, list, minimal, spec, xUnit). Plugins that provide additional report formats can also be installed.
If an automated test fails, but you cannot reproduce the failure manually, there may be an issue with the script. The most effective way of addressing those issues is by debugging the test session. For this purpose, TestCafe Studio implements all the means necessary to effectively troubleshoot test execution.
The Debug action stops a test at a desired moment.
The Debug Mode allows you to run the entire test step-by-step.
The Pause the test when it fails option stops a test the moment it fails.
When a test is paused, you can explore the tested page with developer tools, interact with it, or step over to the next action (if the test has not failed).