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.clicktriggered theclickevent twice (#3645) - Fixed a regression that prevented TestCafe from checking
checkboxinputs witht.click(#3482) - TestCafe TypeScript definitions no longer cause the
Cannot find namespace 'NodeJS'error (#3719) - TestCafe no longer removes the
Authorizationheader when Fetch API is used (testcafe-hammerhead/#2020) - TestCafe now provides correct values for the
form.elements.lengthproperty (testcafe-hammerhead/#2009) - Fixed the
Invariant ViolationReact error caused by TestCafe Hammerhead (testcafe-hammerhead/#2000) - Fixed a regression that disabled the
IE=edgemeta tag (testcafe-hammerhead/#1963) - Fixed an issue that prevented
t.setFilesToUploadfrom raising thechangeevent on some file inputs (testcafe-hammerhead/#2007)