E2E Flake in Develop
See original GitHub issueDescribe the bug
E2E flake in last 7 merged
commits in develop
- Failed: undefined
-
Full exploration editor should navigate multiple states correctly, with parameters
-
Full exploration editor should prevent going back when help card is shown
Maybe fixed by https://github.com/oppia/oppia/pull/15819
- All workflow failing (no logs)
- Expected $.length = 2 to equal 0.
- Core exploration functionality should display plain text content
- When account is deleted it should request account deletion
- Classroom page functionality should search for explorations from classroom page
- Topics and skills dashboard functionality should assign, unassign, create and delete a skill
- ExplorationFeedback should add feedback to an exploration
- Failed: stale element reference: element is not attached to the page document
- Full exploration editor should use hints and solutions in an exploration
- PR#1 additionalPlayerFeatures (May be introduced in #15806)
- PR#2 additionalPlayerFeatures (May be introduced in #15806)
Issue Analytics
- State:
- Created a year ago
- Comments:17 (16 by maintainers)
Top Results From Across the Web
Why end-to-end tests are flaky, and how to fix them
Every time a test flakes, a developer needs to investigate whether the failure is true or false. If the "flake rate" of your...
Read more >End to End Tests · oppia/oppia Wiki - GitHub
New contributors, who are often brand-new to open source software development, can be discouraged by flakes. When they see a failing E2E ......
Read more >Fixed "play later" E2E Flake - Google Groups
We recently merged #14822 to fix the "play later" end-to-end test flake. If tests are failing on your PR with that flake, please...
Read more >Flaky Test Management with Cypress - GitNation
Flaky Test Management with Cypress ... This workshop is for Cypress users who want to step up their game against flake in their...
Read more >Flaky Tests: Getting Rid Of A Living Nightmare In Testing
Even though end-to-end tests are more prone to being flaky, I've experienced them in all kinds of tests: unit tests, functional 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
(1), (2), and (3) are fixed. We didn’t directly fix (6), but we haven’t seen it in a while
Thanks so much @heyimShivam, this is really helpful! I took a quick look.
For 5), isn’t that a “Unhandled promise rejection: RequestError: read ECONNRESET” flake? In general always look at the first thing that occurs – if an earlier test fails then later ones may fail with stuff like “Login page did not load” but that is not the “real” flake.
The one that we haven’t seen before is 1). It seems related to setContent() so maybe it’s a residual flake after the recent fix in #15806. Thanks for raising it – I’ll bring it up with Chris tomorrow.