test-plan-case-implement¶
Generate executable test automation code (pytest, Go, Jest, etc.) from TC-*.md test case specifications. Runs placement analysis to determine component repo vs downstream E2E repo placement, loads repository conventions from odh-test-context, generates test files in parallel via sub-agents, scores quality with a 5-criteria rubric, and auto-revises low-scoring functions. Supports selective implementation via --test-cases flag.
Plugin: test-plan | User-invocable
Contract¶
Implement backend test-case specifications as executable pytest code in the selected target test repository.
Identity
Functions
generate
Success
- Maps cases to destination files, collects complete generated files and writes only the planned destinations.
- Updates test-case automation metadata with the implementation results.
Optimization Targets
Invariants
Must Preserve
- Skip TC-UI cases and preserve existing target test code.
- Inspect repository code without importing target repository dependencies.
Fixed Context
documentsskills/test-plan-case-implement/SKILL.md, scripts/map_test_files.py, skills/test-plan-score-test-function/prompts/score-test-function.md
knowledgetask_inputtask_private
Traceability
Diagram¶
Arguments¶
/test-plan-case-implement <FEATURE_SOURCE> [--test-cases TC-ID,TC-ID] [--target-repo PATH]
| Argument | Required | Default | Description |
|---|---|---|---|
FEATURE_SOURCE |
- | Feature directory, GitHub PR URL, or GitHub branch containing test case artifacts | |
--test-cases |
- | Comma-separated list of specific test case IDs to implement (e.g., TC-API-001,TC-E2E-001) | |
--target-repo |
- | Override auto-detected target repository path or URL |
Usage¶
/test-plan-case-implement features/notebooks/RHAISTRAT-400-notebook-spawning
/test-plan-case-implement https://github.com/org/repo/pull/7
/test-plan-case-implement features/notebooks/RHAISTRAT-400 --test-cases TC-API-001,TC-API-002
/test-plan-case-implement features/notebooks/RHAISTRAT-400 --target-repo ~/Code/opendatahub-tests