Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fix navigation_spec "page load" flaky test.
See original GitHub issueCurrent behavior:
navigation_spec does not log "page load" events is really flaky.
Desired behavior:
It should always pass.
Steps to reproduce: (app code and test code)
It fails a lot on PR.
Versions
develop.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
How to Fix Flaky Tests - Semaphore CI
The first appearance of a flaky test is the best moment to fix it. Maybe the test is new, or a recent commit...
Read more >Flaky Tests: Getting Rid Of A Living Nightmare In Testing
A common environment-side cause is resource leaks: Often this would be an application under load, causing varying loading times or unexpected ...
Read more >6 Steps to Find and Fix Flaky Automated Tests — Ranorex Blog
6 Steps to Find and Fix Flaky Automated Tests · 1. Start small · 2. Run tests regularly · 3. Identify unstable tests...
Read more >How to avoid Flaky Tests : Methods - BrowserStack
1. Abandon the Sleep. Almost all automated tests must wait for a web page, app, or at least certain web elements to load...
Read more >Flaky tests - GitLab Docs
Resolution: Fix the test to not assume that the dataset is in a particular ... It could be to wait for requests to...
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 Free
Top 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
I learned that it’s related to the execution order of events and promises. But needs to research more about how to fix it.
Released in
3.8.3.This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v3.8.3, please open a new issue.