Tests randomly fails on timeout to find an element by attribute on v4.5.0
See original GitHub issueCurrent behavior:
On running our test suite in Cypress v4.5.0, we get random fails whenever the test suite runs in our CI environment (Drone - custom Node v12 docker image - running electron headless).
Examples of two independent runs failing in different tests:
All tests pass when running locally either on chrome and in headless electron. Downgrading to v4.4.1
fixes the issue in our CI.
Desired behavior:
All tests pass independent of version and environment.
Versions
- Cypress:
v4.5.0
- OS: Linux Docker - Node 12 custom image
- Browser - Headless Electron
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:24 (7 by maintainers)
Top Results From Across the Web
cypress.io: contains() not waiting for element - Stack Overflow
contains('Test item 1') is finding something, despite it not yet being visible. cypress will throw an exception and fail the test if it...
Read more >9 Understanding timeouts - Testing Angular Applications
Understanding and avoiding the causes of timeout errors in Protractor; ... 1) the contact list should find the title - Failed: No element...
Read more >Top 10 Selenium Exceptions and How To Handle These ...
In this case, the test will fail because the WebDriver could not find the element. In this case, StaleElementReferenceException will be thrown.
Read more >3 Practices to Reduce Flakiness in Cypress Tests - Atomic Spin
Flaky tests can be difficult to identify and troubleshoot. Here are a few practices to reduce flakiness when using Cypress tests.
Read more >Attributes - NUnit Docs
NUnit uses custom attributes to identify tests. All NUnit attributes are contained in the NUnit.Framework namespace. Each source file that contains tests ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue is closed as no one has provided a way to reproduce it, so there is no solution avaialable. If you can provide a way to reproduce, we’ll take a look at it.
it’s reproducible in a way, that the tests relying on cy.route() and cy.wait() fails randomly in CI (for me the tests are running successfully locally)