Opus Vault

proposal-test-section-template

2 min read

Proposal: Update Test Section in Feature Request Template

What

Update the ## Test section in vault/_templates/feature-request.md to support three test types: manual (mv), automated (opus), and smoke (opus/smoke).

Why

FR-002 revealed that tests fall into three distinct categories:

  • Manual (mv): User runs once to validate behavior before marking FR as done
  • Automated (opus): Deterministic checks (pytest, data validation) that opus runs weekly
  • Smoke (opus): AI self-checks — opus tests its own behavior, indicative but not proof

The current template has a single flat table with no distinction between these types.

Spec

Replace the current Test section:

## Test
 
 
| Test | Expected | Actual  | Last |
| ---- | -------- | ------- | ---- |
| ...  | ...      | pending | -    |

With:

## Test
 
### Manual tests (mv — run once to mark FR as done)
 
| Test | Expected | Actual  | Last |
| ---- | -------- | ------- | ---- |
| ...  | ...      | pending | -    |
 
### Automated tests (opus — run periodically)
 
| Test | Expected | Actual | Last |
| ---- | -------- | ------ | ---- |
| ...  | ...      | pending | -   |
 
### Smoke tests (opus — run periodically, indicative only)
 
| Test | Expected | Actual | Last |
| ---- | -------- | ------ | ---- |
| ...  | ...      | pending | -   |

Notes:

  • Not every FR needs all three subsections — use only what applies
  • Manual tests are the gate for marking an FR as done
  • Automated tests are deterministic (pytest, data checks) for ongoing health
  • Smoke tests are AI self-checks — opus tests its own behavior, indicative but not proof

Impact

  • vault/_templates/feature-request.md — update Test section
  • Existing FRs are not affected (template change is forward-looking)

Graph View