Skip to content

Build/Test Tools: Run the plugins E2E spec in parallel. - #16128

Open
adimoldovan wants to merge 2 commits into
WordPress:trunkfrom
adimoldovan:e2e/plugins-parallel
Open

adimoldovan wants to merge 2 commits into
WordPress:trunkfrom
adimoldovan:e2e/plugins-parallel

Conversation

@adimoldovan

Copy link
Copy Markdown

Trac ticket: https://core.trac.wordpress.org/ticket/66392

This moves plugins.test.js from the serial project to parallel.

The 3 tests in the spec upload, activate, replace and delete the same fixture plugin. The parallel project runs tests from one file at the same time, so the tests now share a PLUGINS lock and run one at a time.

No other spec in parallel changes plugins. The README now says that a spec in parallel that installs, deletes, activates or deactivates a plugin must hold PLUGINS, because WordPress writes back the full active_plugins list and two writes at the same time can lose one change.

Testing Instructions

  1. Start the local environment: npm run env:start && npm run env:install.
  2. Run npx playwright test --config tests/e2e/playwright.config.js --project=parallel plugins.test --repeat-each=3. All 9 tests pass.
  3. Run npx playwright test --config tests/e2e/playwright.config.js --project=parallel --repeat-each=2. All tests pass, and the run includes plugins.test.js.

Use of AI Tools

AI assistance: Yes

Give the plugin management tests a `PLUGINS` lock, so that only one runs at a time. Move the spec to the parallel Playwright project. A parallel spec that installs, deletes, activates or deactivates a plugin must hold this lock.

See #66392.
@adimoldovan adimoldovan self-assigned this Nov 20, 2026
@adimoldovan
adimoldovan marked this pull request as ready for review November 20, 2026 13:01
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props adrianmoldovanwp.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub or WordPress.org user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant