It - [Title] - Iteration Record Document
Plan: Pl[No]-[Title] · Code: Cd[No]-[Title]
Execution Overview
- Scope / slice:
- Trigger: first test execution
- Start / end time:
- Runtime environment (optional): Node / OS / CPU / memory (summary)
- Main commands (optional): test / quality check commands and versions
- Result summary: passed / failed / skipped / duration (summary)
- Notes:
1) Initial Test Result
Test Statistics
| Metric | Value | Status |
|---|
| Total tests | | |
| Passed | | ✅ |
| Failed | | ❌ |
| Skipped | | |
| Execution time | | |
Failed Test Case List
- Test identifier: [file#testName] - error summary (including key stack / log path)
- ...
2) Issue Analysis and Classification
Analysis Table
| Test identifier | Type | Severity | Root cause | Impact scope | Relation to Plan acceptance | Notes |
|---|
| Function / Logic / Contract / Performance / Environment | | | | | If test adjustments are needed, explain the reason and minimum change |
3) Fix Implementation (Codex Autonomous Fixing)
Fix Highlights
| Test / issue | Change summary | Involved files | Contract / type sync (if any) | Impact scope |
|---|
| | | | |
Note: record only substantive change summaries and keep the document readable and consistent.
4) Retest Result
Test Statistics (Comparison)
| Metric | First run | This run | Delta |
|---|
| Total tests | | | |
| Passed | | | |
| Failed | | | |
| Skipped | | | |
| Execution time | | | |
Conclusion
- Remaining issues and reasons:
- Evidence and records (optional): screenshot / log / replay script path
5) Quality Checks (pnpm)
Check Results
- typecheck: pass / fail (summary)
- lint: pass / fail (summary)
- format:check: pass / fail (summary)
6) Acceptance Conclusion and Follow-up Suggestions
Acceptance Mapping (Plan Acceptance Checklist)
Unresolved / Deferrable Items
- Item: reason and impact; suggested timing for handling
Created on: date '+%Y-%m-%d'