Skip to content

Build/Test Tools: Run the theme management E2E tests in parallel. - #16127

Draft
adimoldovan wants to merge 2 commits into
WordPress:trunkfrom
adimoldovan:e2e/themes-split
Draft

adimoldovan wants to merge 2 commits into
WordPress:trunkfrom
adimoldovan:e2e/themes-split

Conversation

@adimoldovan

Copy link
Copy Markdown

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

This moves most of themes.test.js from the serial project to parallel.

  • Only "activates an installed theme from its card" changes the active theme. It moves to theme-activation.test.js, which stays in SERIAL_SPECS.
  • The other four tests install, replace, delete and search one fixture theme. They hold the lock E2E_TEST_THEME, so two of them never use the fixture theme at the same time. No other parallel spec installs themes or changes the active theme.
  • The helpers that upload and delete the fixture theme move to tests/e2e/utils/themes.js, so both specs can use them.

Testing Instructions

  1. Start the local environment: npm run env:start && npm run env:install.
  2. Run npm run test:e2e -- --project=parallel specs/themes.test.js --repeat-each=3. All 12 runs pass.
  3. Run npm run test:e2e -- --project=serial. All tests pass, and the run includes theme-activation.test.js.

Use of AI Tools

AI assistance: Yes

Move the theme activation test to its own serial spec, because it changes the active theme. The other tests only install, replace, delete and search the fixture theme. They now run in parallel and share one lock.

See #66392.
@adimoldovan adimoldovan self-assigned this Nov 20, 2026
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