forked from mengyxu/noob-components
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.7 KiB
1.7 KiB
| name | description |
|---|---|
| improve-ut | Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified. |
Improve Unit Tests (UT)
Use this skill to improve test coverage after code changes.
Usage
$improve-ut
Source of Truth
Discover and read unit-test specs dynamically:
# Discover available packages and their spec layers
python3 ./.trellis/scripts/get_context.py --mode packages
Look for packages with unit-test spec layer in the output. For each discovered unit-test/ directory, read all relevant spec files inside it (for example index.md, conventions.md, integration-patterns.md, mock-strategies.md).
If this skill conflicts with the unit-test specs, the specs win.
Execution Flow
- Inspect changed files:
git diff --name-only
- Decide test scope using unit-test specs:
- unit vs integration vs regression
- mock vs real filesystem flow
- Add/update tests using existing project test patterns
- Run validation:
pnpm lint
pnpm typecheck
pnpm test
- Summarize decisions, updates, and remaining test gaps.
Output Format
## UT Coverage Plan
- Changed areas: ...
- Test scope (unit/integration/regression): ...
## Test Updates
- Added: ...
- Updated: ...
## Validation
- pnpm lint: pass/fail
- pnpm typecheck: pass/fail
- pnpm test: pass/fail
## Gaps / Follow-ups
- <none or explicit rationale>