Fix failing and flaky E2E tests#360
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #360 +/- ##
==========================================
Coverage 57.70% 57.70%
Complexity 617 617
==========================================
Files 46 46
Lines 3173 3173
==========================================
Hits 1831 1831
Misses 1342 1342
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
What?
Fixes flaky E2E image edit tests. Also updates some tests based on the new Connectors markup that's in WordPress
trunkWhy?
Some of the image edit E2E tests tend to be flaky, sometimes passing, sometimes not. Seems to be most flaky in our pipeline runs.
Also have some tests that started failing due to markup changes to the Connectors screen recently merged into WordPress
trunkHow?
Ensure we wait properly for click events to happen. Update our selectors
Use of AI Tools
Used Cursor running GPT-5.3 Codex to investigate and fix the issue. Ran E2E tests myself locally multiple times to verify the fix
Testing Instructions
n/a. Just ensure E2E tests pass