23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
|
# Implementation: fix-test-plan-phase-mapping
|
||
|
|
|
||
|
|
## Bug
|
||
|
|
Both `status.py:_infer_state_from_artifacts()` and the dashboard's `determine_task_state()` mapped `TEST_PLAN.md` to the `implement` phase. But `TEST_PLAN.md` is produced during the `test_design` phase, not `implement`. This caused:
|
||
|
|
- `--upgrade` to bootstrap incorrect `.state` for tasks with TEST_PLAN.md
|
||
|
|
- Dashboard to show `IMPLEMENT` instead of `TEST_DESIGN` for tasks that have a test plan but no implementation yet
|
||
|
|
|
||
|
|
## Fix
|
||
|
|
Changed the mapping in both locations:
|
||
|
|
1. `scripts/status.py:348-349`: `TEST_PLAN.md` → `test_design` (was `implement`)
|
||
|
|
2. `automaton/dashboard/core/task.py:548-549`: `TEST_PLAN.md` → `TaskState.TEST_DESIGN` (was `TaskState.IMPLEMENT`)
|
||
|
|
|
||
|
|
## Files Changed
|
||
|
|
- `scripts/status.py` (line 348-349): Changed return value from `"implement"` to `"test_design"`
|
||
|
|
- `automaton/dashboard/core/task.py` (line 548-549): Changed return from `TaskState.IMPLEMENT` to `TaskState.TEST_DESIGN`
|
||
|
|
- `tests/test_task.py`: Updated `test_implementation_from_test_plan` and `test_test_plan_shows_implement` to assert `TEST_DESIGN` instead of `IMPLEMENT`
|
||
|
|
|
||
|
|
## Tests
|
||
|
|
- `test_implementation_from_test_plan`: Now asserts `TaskState.TEST_DESIGN`
|
||
|
|
- `test_test_plan_shows_test_design` (renamed from `test_test_plan_shows_implement`): Asserts `TaskState.TEST_DESIGN`
|
||
|
|
- `test_test_plan_maps_to_test_design` in `test_status.py`: Verifies `--upgrade` infers `test_design` for TEST_PLAN.md
|
||
|
|
- All 249 tests pass
|