Software Orchestrator
5769c1cd22
- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung) - 25 Tests gruen (Pytest) - block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block) - 4 Restbaustellen gefixt - DB-Schema: plugin_settings-Tabelle hinzugefuegt - 3 Schattenprojekte aus DB geloescht - Plan v3 + Refactor-Plan + Worklog dokumentiert
1.3 KiB
1.3 KiB
name, description, tags
| name | description | tags | |||
|---|---|---|---|---|---|
| test-validation | Use existing test/build tooling for validation - no invented commands. |
|
Test Validation
Purpose
Run the project's existing test and build tooling to validate a change, without inventing new commands.
When to Use
- After any implementation block
- Before declaring a feature complete
- Before a release
- When verifying a bug fix
When Not to Use
- When no test framework exists (create one first, see implementation_engineer)
- For purely documentation changes (no test needed)
Procedure
- Discover test framework from package.json, requirements.txt, Makefile, etc.
- Discover build command from the same files
- Run tests using the discovered command (e.g.,
npm test,pytest,make test) - Run build using the discovered command (e.g.,
npm run build,make build) - Capture pass/fail counts and detailed failure output
- If failures, classify and delegate to test_debug_engineer for root cause
Quality Gates
- Tests pass (no failures, no skips without justification)
- Build succeeds without warnings (or warnings documented)
- Type check passes (e.g.,
tsc --noEmit,mypy)
See Also
- Tool:
terminal(for running test commands) - Subagent:
test_debug_engineer