Plugin Check and PHPCS
Run the official Plugin Check workflow in wp-admin, then reproduce coding-standard checks from the CLI with PHPCS/WPCS.
WordPress.org-oriented QA included
A WordPress plugin lab from code to compatibility.
Create an isolated site, work against the host-mounted plugin source, run browser and CLI checks, inspect runtime behavior and discard the environment when the test is complete.
One complete loop
Build, inspect, compare, reset.
Spawn a Development site
Choose the Development blueprint and the PHP runtime your plugin needs. WordPress arrives with debug mode and the QA toolkit enabled.
Bring in the plugin
Clone or mount source under the site's host-visible
wp-content/pluginsdirectory, or use the cockpit file browser for focused changes.Run WordPress.org checks
Use Plugin Check in wp-admin, PHPCS with WordPress Coding Standards and PHPCompatibilityWP from the container.
Analyse and observe
Run PHPStan with WordPress stubs, inspect queries and hooks through Query Monitor, and review scheduled tasks with WP Crontrol.
Exercise real behavior
Use different roles, trigger plugin flows and inspect captured HTML email, headers and attachments in the site's Mailpit inbox.
Repeat safely
Switch PHP, restore a snapshot, reset or destroy the site. A separate environment keeps another test baseline untouched.
Included toolchain
Browser feedback and scriptable checks.
PHPCompatibilityWP
Scan syntax and API compatibility for an explicit target range before running the plugin under each actual PHP runtime.
PHPStan with WP stubs
Catch type and control-flow problems with a preconfigured WordPress-aware static-analysis baseline.
Runtime inspection
Query Monitor, WP Crontrol, User Switching, Xdebug and the debug log cover queries, hooks, scheduled events, roles and step-through debugging.
Code stays reachable
Edit with your tools. Execute inside the environment.
Plugin and theme source is bind-mounted on the host, while Composer, Node, WP-CLI and the PHP QA tools execute in the site's PHP container. The cockpit also provides a WP-CLI console and scoped file browser for browser-only work.
Know the boundary
A development lab, not hosted CI.
The toolchain is scriptable and suitable for repeatable checks, but SpawnWP does not provide a hosted CI service or automatically run your repository pipeline. You control the server, source checkout and automation.
Build the first environment
Give every plugin test a clean WordPress site.
Review server and DNS requirements before installing the self-hosted lab.