| name | run-tests |
| description | Runs and interprets Pixel Creator tests after implementation or when diagnosing a regression. Use when verification, test failures, regression analysis, or test-suite status is the primary task. |
Run Pixel Creator Tests
Procedure
- Inspect
package.json and the project's actual test commands.
- Run the smallest relevant test set first.
- If targeted tests pass, run the broader suite when appropriate.
- Inspect failures rather than immediately modifying code.
- Determine whether each failure is:
- caused by the current change;
- an existing failure;
- an environment/tooling issue;
- an unrelated test failure.
- Report the result precisely.
Rules
Do not weaken tests to make them pass.
Do not delete tests without explicit justification.
Do not change production behavior merely to satisfy an incorrect test.
When a test exposes a real contract change, determine whether the implementation or the test should change.
Output
Report:
- command(s) executed;
- number of tests passed/failed when available;
- relevant failures;
- likely cause;
- whether the failure blocks the requested change.