Files
gps-denied-onboard/.cursor/skills/plan/steps/05_test-specifications.md
T
Oleksandr Bezdieniezhnykh 6044a33197 chore: WIP pre-implement
Bundled hygiene commit before cycle-3 /implement (AZ-776, AZ-777). Mixes
two concerns by user choice (autodev option B):

- Cycle-3 autodev artifacts not yet committed by Step 9 (new-task):
  task specs for AZ-776 / AZ-777 under _docs/02_tasks/todo/ and the
  updated _docs/02_tasks/_dependencies_table.md.
- Accumulated skill / rule tooling maintenance under .cursor/ (skills:
  autodev, code-review, decompose, deploy, implement, new-task, plan,
  refactor, retrospective, test-spec; rules: coderule, cursor-meta,
  meta-rule, testing; new release skill scaffolding).
- Autodev bootstrap state: _docs/_autodev_state.md (step 10 in_progress)
  and _docs/_process_leftovers/2026-05-11_d_cross_cve_1_opencv_pin_deferred.md
  (replay timestamp refreshed; gtsam 4.2 still numpy<2-only).

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-21 13:14:11 +03:00

1.0 KiB

Step 5: Test Specifications

Role: Professional Quality Assurance Engineer

Goal: Write test specs for each component achieving the canonical minimum acceptance-criteria coverage (currently 75% — see .cursor/rules/cursor-meta.mdc Quality Thresholds; do not restate a different number here)

Constraints: Test specs only — no test code. Each test must trace to an acceptance criterion.

  1. For each component, write tests using templates/test-spec.md as structure
  2. Cover all 4 types: integration, performance, security, acceptance
  3. Include test data management (setup, teardown, isolation)
  4. Verify traceability: every acceptance criterion from acceptance_criteria.md must be covered by at least one test

Self-verification:

  • Every acceptance criterion has at least one test covering it
  • Test inputs are realistic and well-defined
  • Expected results are specific and measurable
  • No component is left without tests

Save action: Write each components/[##]_[name]/tests.md