Repository navigation
Build/Test Tools: Run E2E specs in parallel and serial projects. - #14897
Draft
adimoldovan wants to merge 7 commits into
Draft
adimoldovan wants to merge 7 commits into
adimoldovan wants to merge 7 commits into
Conversation
The E2E suite runs on one worker. Split it into two Playwright projects: - `parallel` runs 15 spec files on several workers. - `serial` runs the 6 specs that break the site for other tests, on one worker. Each project has its own npm script. CI runs each project in a separate matrix job, so a failure in one project does not hide the results of the other.
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
The base config from `@wordpress/scripts` sets `workers: 1` for the whole run, so the `parallel` project ran on one worker. Set `workers: '50%'` at the top level. This is the Playwright default. Move the 7 specs that delete all posts or media to `serial`. On several workers, they delete content that tests on other workers use.
… project. Add an `all` project that runs every spec on one worker. It is the only default project, so `npm run test:e2e` runs the whole suite serially, as before. Set `default: false` on `parallel` and `serial`, which needs Playwright 1.64. CI selects them with `--project`, so the two npm scripts are no longer needed. Move `themes.test.js` to `serial`, because it changes the active theme for the whole site.
Release branches call the `trunk` copy of the reusable E2E workflow, and their Playwright configs have no `parallel` or `serial` project. Add a `test-group` input to the reusable workflow. When it is empty, the workflow runs `npm run test:e2e` as before. `end-to-end-tests.yml` sets it from its own matrix. Document `--shuffle` in the E2E README as a check for new specs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two Playwright projects so that CI can run part of the E2E suite in parallel. Today the whole suite runs on one worker, because
@wordpress/scriptssetsworkers: 1.parallelruns 10 spec files on several workers, one for every two CPU cores. Tests inside one file still run in order.serialruns the other 14 spec files on one worker. These specs break the site for other tests or change content that other tests use. For example,install.test.jsdrops the database tables, andedit-posts.test.jsdeletes all posts.A third project,
all, is set as default and runs every spec on one worker as before. It is added for convenience, to keep the existingnpm run test:e2ecommand running the whole suite.The config sets
workers: '50%', the Playwright default, to replace theworkers: 1from@wordpress/scripts.In CI,
parallelandserialrun in separate matrix jobs.Testing
npm cinpm exec --no -- playwright install chromiumnpm run env:start && npm run env:installnpm run test:e2e -- --listlists 101 tests in 24 files, all in theallproject.npm run test:e2e -- --project=serial --listlists 72 tests in 14 files.npm run test:e2e -- --project=parallel --listlists 29 tests in the other 10 files.npm run test:e2e -- --project=parallel, thennpm run test:e2e -- --project=serialTrac ticket: TBD
Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Config, scripts, workflow change, test runs and this description. I reviewed the result.
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.