| name | wallaby-testing |
| description | Check test status and debug failing tests using Wallaby.js real-time test results. Use after making code changes to verify tests pass, when checking if tests are failing, debugging test errors, analyzing assertions, inspecting runtime values, checking coverage, updating snapshots, or when user mentions Wallaby, tests, coverage, or test status. |
| compatibility | Requires Wallaby.js VS Code extension installed and running |
| metadata | {"author":"wallaby.js","version":"1.0"} |
Wallaby Testing Skill
Open and apply the reference files for the relevant section before working.
Core Rules
- Use Wallaby first after code changes, when checking test status, debugging failures, inspecting runtime values, reviewing coverage, or updating snapshots.
- Start with failing-test or all-test queries to get test IDs before using test-scoped tools.
- Prefer runtime values and covered-line data over guessing when the failure cause is unclear.
- Make targeted fixes based on the failing test, stack trace, coverage, and runtime values.
- Verify the specific fixed test and then check all failing tests for regressions.
- Update snapshots only when the snapshot change is expected, and verify again afterward.
- See ./rules/tool-reference.md for available Wallaby tools and required inputs.
- See ./rules/debugging-workflow.md for the step-by-step debug workflow.
- See ./examples/assertion-failure.md for an assertion failure example.
