Testing Strategy
How unit, integration, contract, browser, security, and edition tests fit together.
Select the narrowest test that proves the changed boundary, then run the phase gate.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
API Vitest tests cover services and routes, integration tests require disposable dependencies, browser tests cover web/admin routes, and edition checks confirm both distributables retain identity and isolation.
| Check | Source-backed expectation |
|---|---|
| Scope | Skipped tests require a recorded reason and must not be silently counted as green coverage. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm test |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm test
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.