User runCLI and unit tests to test plugins and themes #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Run Asyncify and JSPI modes simultaneously instead of sequentially - Smart port allocation: Asyncify uses workerId, JSPI uses workerId + MAX_CONCURRENCY - Reduces test time per item from ~4min to ~2min (~50% improvement) - Configurable via single MAX_CONCURRENCY constant (default: 8) - Supports MAX_CONCURRENCY × 2 concurrent Playground instances - No port conflicts, scales automatically with concurrency setting
bgrgicak
changed the title
There was a problem hiding this comment.
Pull Request Overview
This PR refactors the testing infrastructure to use Vitest and @wp-playground/cli for comprehensive integration tests of WordPress plugins and themes. Previously only basic boot tests were supported; now the system can validate WordPress boot, post creation, wp-admin loading, and plugin/theme activation.
Key Changes:
- Introduced Vitest-based test framework with
wordpress.spec.tsintegration tests - Implemented dual-mode testing (Asyncify and JSPI) that runs in parallel for each item
- Added error log parser to extract and categorize PHP, SQL, and Playground runtime errors
Reviewed Changes
Copilot reviewed 8 out of 10 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| vitest.config.ts | Configures Vitest with 2-minute timeouts and exclusion patterns |
| src/test/unit/wordpress.spec.ts | Core integration tests for WordPress boot, post creation, wp-admin, and plugin/theme activation |
| src/test-runner.ts | Spawns Vitest with mode-specific Node.js flags (JSPI vs Asyncify) |
| src/test-batch.ts | Orchestrates batch testing with concurrency control and aggregates results from both modes |
| src/lib/log-parser.ts | Parses error logs and test results to generate structured error reports |
| package.json | Updates dependencies to support new testing framework |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The wordpress-develop directory was registered as a submodule in Git's index but not in .gitmodules, causing CI failures when trying to initialize submodules. This directory is not used by the playground compatibility tester and is excluded from tests. Fixes CI error: fatal: No url found for submodule path 'wordpress-develop' in .gitmodules 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 7 out of 9 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for the change, related issues
The previous testing infrastructure only supported basic boot tests. This refactor introduces Vitest as the test framework, enabling us to write comprehensive integration tests for WordPress plugins and themes.
Implementation details
Test Framework:
@wp-playground/clisrc/test/unit/wordpress.spec.ts- validates boot, post creation, wp-admin loading, plugin/theme activationvitest.config.tswith 2-minute timeouts for WordPress installationsrc/test-runner.tsspawns vitest with mode-specific Node.js flags--experimental-wasm-jspiflagError Parser (
src/lib/log-parser.ts):Testing instructions
Run unit tests:
npm testTest single item:
Test a batch:
Expected output:
TODO