Skip to content

STD-DEV-002: Verification & Seeding Protocol

1. Context

To ensure system stability through rigorous "AutoTester" verification and reproducible "DataSeeder" states.

2. The Standard (The Floor)

  • [MUST] Traceability: Tests MUST include @cap, @persona, and @env metadata tags.
  • [MUST] Tooling: Use Vitest for Unit Tests, Playwright for E2E.
  • [MUST] Naming: Files MUST be .test.ts (Unit), .spec.ts (E2E), or .verify.ts (Script).
  • [MUST] Idempotency: Seeding scripts MUST be idempotent (UPSERT logic).
  • [MUST] Accessibility: PRs with Critical A11y violations (Axe) MUST be blocked.

3. Best Practices (The Path)

  • [SHOULD] AutoTester Family: Use AutoTester-Dev for local loop, AutoTester-Sprint for release gates.
  • [SHOULD] DataSeeder Family: Use DataSeeder-Local for rapid dev, DataSeeder-Gold for high-fidelity restore.
  • [SHOULD] Aesthetic Persistence: Use Visual Regression testing for "Gold Workbenches".

5. Version History

Version Date Author Change
1.0 2026-01-25 AI Extracted from Engineering Handbook

Version History

Version Date Author Change
0.1.0 2026-01-26 Antigravity Initial Audit & Metadata Injection