DEV.co
Open-Source Testing · lucatume

wp-browser

wp-browser is a PHP testing framework that integrates Codeception with WordPress to enable end-to-end, integration, and unit testing for WordPress sites, plugins, and themes. It provides quick setup with sensible defaults (SQLite, built-in PHP server, Chromedriver) and has been maintained actively for over a decade.

Source: GitHub — github.com/lucatume/wp-browser
638
GitHub stars
85
Forks
PHP
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorylucatume/wp-browser
Ownerlucatume
Primary languagePHP
LicenseMIT — OSI-approved
Stars638
Forks85
Open issues0
Latest release3.8.1 (2026-07-05)
Last updated2026-07-05
Sourcehttps://github.com/lucatume/wp-browser

What wp-browser is

wp-browser is a Codeception module for WordPress testing that abstracts away test environment setup by offering opinionated defaults: SQLite Database Integration plugin for data isolation, PHP built-in server for local hosting, and Chromedriver for browser automation. It builds on PHPUnit and Codeception, supporting WordPress-native testing patterns without extensive custom infrastructure.

Quickstart

Get the wp-browser source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/lucatume/wp-browser.gitcd wp-browser# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Plugin and Theme Development

Rapidly test custom plugins and themes against WordPress with isolated test environments. The framework automatically installs WordPress in a test directory and symlinks plugins/themes, making CI/CD integration straightforward without manual database or server management.

WordPress Site Integration Testing

Run integration and end-to-end tests on configured WordPress installations using the same tool. Default SQLite setup eliminates database overhead while Chromedriver enables full browser-based testing of custom post types, taxonomies, and user workflows.

Legacy WordPress Test Suite Migration

Convert older WordPress test suites or manual testing to automated Codeception-based tests. The framework's 10-year stability and WordPress-native conventions reduce learning curve for teams already familiar with WordPress internals.

Implementation considerations

  • Verify PHP sqlite3 extension is enabled on all development and CI machines before adopting quick-start setup; otherwise fallback to custom .env configuration is mandatory.
  • Test environment isolation via SQLite is suitable for unit and integration tests but may not reflect production MySQL/MariaDB behavior under heavy load or with complex queries.
  • Chromedriver automation requires a local Chrome/Chromium installation; headless environments need explicit driver configuration or Docker integration.
  • WordPress installation is bootstrapped into tests/_wordpress; ensure sufficient disk space and that symlink permissions are correctly configured in CI/CD agents.
  • Version 4 migration from version 3 is documented but non-trivial; audit your existing test suite for breaking changes before upgrading.

When to avoid it — and what to weigh

  • Non-PHP Test Infrastructure — wp-browser is PHP-specific and Codeception-dependent. If your team uses JavaScript-first testing (Jest, Cypress) or non-PHP CI/CD, integrating this adds a secondary test pipeline.
  • Multi-Database or Complex Staging Workflows — Default configuration uses SQLite for simplicity. Production environments using MySQL/MariaDB or complex data fixtures may require significant custom configuration beyond the quick-start setup.
  • Headless or API-Only Testing at Scale — While wp-browser supports API testing via Codeception, it is optimized for browser-driven tests. If your primary need is API contract testing or performance testing, dedicated tools (RestAssured, k6) may be more efficient.
  • Minimal PHP Version or Missing sqlite3 Extension — Quick setup requires PHP with sqlite3 extension enabled. Custom PHP environments (containers, restricted hosts) without sqlite3 will require manual configuration or alternative database setup.

License & commercial use

MIT License. Permissive open-source license allowing modification, distribution, and private use with no warranty. Attribution required but no copyleft obligation.

MIT is a standard permissive OSI license suitable for commercial and proprietary projects. No license restriction prevents commercial use, but review your internal software governance policy. No warranty or support is legally guaranteed; contact maintainer directly for support arrangements.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityLow
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Test environments use SQLite by default and local Chromedriver, limiting external exposure. Ensure test database files and Chromedriver instances are not exposed in production. SQLite is suitable for isolated CI/CD runs but not for concurrent multi-user testing. WordPress test installations should be on isolated networks; credential leaks in test fixtures or logs could expose plugin/theme vulnerabilities. No explicit security audit claims are stated in documentation; review plugin ecosystem (e.g., SQLite Database Integration plugin) for any known issues.

Alternatives to consider

PHPUnit with Manual WordPress Test Utilities

Lower-level control and fewer dependencies; suitable if your team prefers minimal abstractions or already has WordPress test infrastructure. Higher setup overhead but no Codeception lock-in.

Playwright (Node.js) or Cypress

Modern browser automation frameworks with better cross-platform support and JavaScript ecosystem. Preferred if team already uses JS-based CI/CD or needs API+UI testing in single language.

LocalWP (desktop) + WP-CLI Scripting

Lightweight alternative for local development and manual testing workflows. Not suitable for automated CI/CD but removes need for complex test environment management in development.

Software development agency

Build on wp-browser with DEV.co software developers

wp-browser eliminates test environment setup overhead. Evaluate integration with your CI/CD pipeline and team PHP skill level. Contact our team to assess fit for plugin, theme, or site projects.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

wp-browser FAQ

Can I use wp-browser with MySQL instead of SQLite?
Yes, but you must skip the quick-start and configure tests/.env manually. SQLite is the default for simplicity; MySQL requires custom database host, credentials, and connection settings. Production parity testing may benefit from MySQL, but test performance overhead increases.
Is wp-browser suitable for continuous integration (GitHub Actions, GitLab CI)?
Yes. Composer-based installation, vendor/bin execution, and SQLite defaults work well in containerized CI. Ensure PHP sqlite3 extension and Chromedriver (or headless browser image) are present in CI environment. Examples are available in documentation.
How does wp-browser handle WordPress database state between test runs?
SQLite database file is typically recreated or reset between test suites; isolation depends on your configuration. PHPUnit transactions or fixtures can further isolate state. Custom MySQL setups require explicit cleanup strategies (fixtures, database reset scripts).
Can I test multiple WordPress multisite configurations?
Not clearly stated in provided documentation. Requires review of advanced configuration documentation or direct contact with maintainer for multisite-specific setup guidance.

Software development & web development with DEV.co

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If wp-browser is part of your open-source testing roadmap, our team can implement, customize, migrate, and maintain it.

Ready to streamline WordPress testing?

wp-browser eliminates test environment setup overhead. Evaluate integration with your CI/CD pipeline and team PHP skill level. Contact our team to assess fit for plugin, theme, or site projects.