CI: Include WP trunk in e2e test runs on PRs#373
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 Core Committers: Use this line as a base for the props when committing in SVN: 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 @@
## trunk #373 +/- ##
============================================
- Coverage 53.88% 52.99% -0.89%
Complexity 4419 4419
============================================
Files 298 298
Lines 39448 39448
============================================
- Hits 21256 20906 -350
- Misses 18192 18542 +350
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:
|
I've noticed that e2e tests are failing when run against WP
trunk. (See e.g. here and here.)This is somewhat unsurprising, since we're currently near the release of WP 7.0, so WP
trunkhas evolved considerably since the latest stable release (6.9.x).It'd be good to preemptively catch problems, so I'm adding back WP
trunkto the test matrix for PRs (rather than only on merge, i.e. after the fact).If we find that e2e tests take to long, we might want to audit them (and e.g. tweak test fixtures and setup, and/or use
test.stepto cover multiple scenarios in one test).