@wordpress/e2e-tests
Advanced tools
This package contains test plugins and mu-plugins used by E2E tests in WordPress.
Note: The E2E tests themselves have been migrated to Playwright and are now located in /test/e2e/.
/plugins/ - Test plugins used by E2E tests/mu-plugins/ - Must-use plugins for test environment configuration/assets/ - Test assets (images, etc.)These plugins and mu-plugins are automatically loaded in the test environment via wp-env. They provide test fixtures and functionality needed for various E2E test scenarios.
For information about writing E2E tests, see the E2E testing guide.
This is an individual package that's part of the Gutenberg project. The project is organized as a monorepo. It's made up of multiple self-contained software packages, each with a specific purpose. The packages in this monorepo are published to npm and used by WordPress as well as other software projects.
To find out more about contributing to this package or Gutenberg as a whole, please read the project's main contributor guide.
FAQs
Test plugins and mu-plugins for E2E tests in WordPress.
The npm package @wordpress/e2e-tests receives a total of 709 weekly downloads. As such, @wordpress/e2e-tests popularity was classified as not popular.
We found that @wordpress/e2e-tests demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 23 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.
Research
/Security News
Malicious dYdX client packages were published to npm and PyPI after a maintainer compromise, enabling wallet credential theft and remote code execution.
Security News
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.