57 lines
1.6 KiB
Markdown
57 lines
1.6 KiB
Markdown
---
|
|
name: ck-test
|
|
description: Run tests locally and analyze the summary report. Use when running unit tests, integration tests, checking test failures, or validating that code changes don't break existing test suites.
|
|
---
|
|
|
|
# Test — Run and Analyze Tests
|
|
|
|
Runs the project's test suite and analyzes results.
|
|
|
|
## When to Use
|
|
|
|
- Running tests after implementing a feature
|
|
- Checking if existing tests pass after a code change
|
|
- Analyzing test failures and understanding what broke
|
|
- Validating a fix resolved a failing test
|
|
|
|
## Don't Use When
|
|
|
|
- Task requires implementing new tests (implement first, then run)
|
|
- CI/CD pipeline already handles automated testing
|
|
|
|
## Execution
|
|
|
|
Delegate to the `tester` sub-process to run tests locally and analyze the summary report:
|
|
|
|
1. Detect the test runner from the project (Jest, Vitest, pytest, Go test, etc.)
|
|
2. Run the full test suite
|
|
3. Analyze failures — identify root cause for each failing test
|
|
4. Report: total tests, passed, failed, skipped, coverage if available
|
|
|
|
## Important Rules
|
|
|
|
- Do NOT start implementing fixes — analyze and report only
|
|
- Do NOT ignore failing tests just to pass the build
|
|
- Do NOT use fake data, mocks, or temporary solutions to force tests to pass
|
|
- Activate relevant skills from the skills catalog as needed during analysis
|
|
|
|
## Report Format
|
|
|
|
```
|
|
## Test Results
|
|
|
|
- Total: X | Passed: X | Failed: X | Skipped: X
|
|
- Coverage: X% (if available)
|
|
|
|
## Failing Tests
|
|
|
|
### test-name
|
|
- File: path/to/test.ts:line
|
|
- Error: [error message]
|
|
- Likely cause: [brief analysis]
|
|
|
|
## Recommendations
|
|
|
|
- [Actionable fix for each failure]
|
|
```
|