An in-range update of testcafe is breaking the build π¨
Closed this issue Β· 1 comments
The devDependency testcafe was updated from 1.4.3
to 1.5.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
testcafe is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v1.5.0
v1.5.0 (2019-9-12)
Enhancements
βοΈ Page Caching Can be Disabled (#3780)
TestCafe may be unable to log in to the tested website correctly if the web server uses caching for authentication pages or pages to which users are redirected after login. See the User Roles topic for details.
If tests fail unexpectedly after authentication, disable page caching in TestCafe.
Use the fixture.disablePageCaching and test.disablePageCaching methods to disable caching during a particular fixture or test.
fixture .disablePageCaching `My fixture` .page `https://example.com`;
test .disablePageCaching ('My test', async t => { /* ... */ });
To disable page caching during the entire test run, use either of the following options:
-
the --disable-page-caching command line flag
testcafe chrome my-tests --disable-page-caching
-
the
disablePageCaching
option in the runner.run methodrunner.run({ disablePageCaching: true });
-
the disablePageCaching configuration file property
{ "disablePageCaching": true }
If tests run correctly without page caching, we recommend that you adjust the server settings to disable caching for authentication pages and pages to which the server redirects from them.
Bug Fixes
- Fixed an error that occured when a selector matched an
<svg>
element (#3684) - Fixed an issue when the
reporter
configuration file option was not applied (#4234) - Fixed a warning message about invalid
tsconfig.json
file (#4154) LiveRunner.stop()
now closes the browsers (#4107)- Quarantined tests now re-run correctly in live mode (#4093)
- Fixed a bug when client scripts were not injected in live mode when it re-executed tests (#4183)
form.elements.length
now returns the correct value for forms with file inputs (testcafe-hammerhead/#2034)- Fixed a bug when images were not displayed in inputs with the
image
type (testcafe-hammerhead/#2116) - Fixed an AngularJS compatibility issue that caused a
TypeError
(testcafe-hammerhead/#2099) - TestCafe now works correctly with servers that use
JSZip
to unpack uploaded files (testcafe-hammerhead/#2115)
Commits
The new version differs by 25 commits.
613eda4
Bump version (v1.5.0) (#4268)
fd57ce4
[docs] Add a changelog for v1.5.0 (#4266)
782ed3a
[docs] Merge new docs for v1.5.0 (#4260)
9093f20
Bump version (v1.5.0-rc.2)
87aad18
Fix wrong options passing for 'disablePageCaching' and 'disablePageReloads' (#4264)
24ff573
Fix crash when using keyboard shortcuts in Live mode (#4258)
e8150ca
Bump version (v1.5.0-rc.1)
fc6c05b
Using debug action in server code step fixed (closes #4245) (#4246)
0fc0e92
svg do not break searching by text (closes #3684) (#4251)
424cf5d
update hammerhead (#4253)
2261912
[docs] Replace keyPress with pressKey
abadd4f
Fix 'Wrong message " The "<option_name>" option from the configuration file will be ignored. "' (close #4234) (#4242)
9bcf470
Browser is correctly closed after the
LiveModeRunner.stop()
method called (closes #4107) (#4243)7a84b98
Fix script injection examples (#4248)
2895b66
bump version (#4241)
There are 25 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After pinning to 1.4.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.