schema0-testing
Testing
STOP — testing is non-skippable.
If you believe tests should be skipped, deferred, or substituted with anything else (browser smoke test, manual verification, "I'll add them after deploy", etc.), you MUST stop and ask the user before making any change. Send exactly this message and wait for a reply:
"I'm proposing to skip mandatory tests because [reason]. Approve?"
You may not decide this unilaterally. The decision to skip is the user's, not yours.
A test todo is complete only when you paste the test runner's output showing pass/fail counts. Other states ("deferred", "covered by smoke test", "called out in summary") are not completion.
Minimum requirement: 3 CRUD tests per entity (create, update, delete via UI). NEVER gut tests to make them pass — fix the source code instead.
Shared Infrastructure
| Type | Location | Runner |
|---|---|---|
| Web | packages/test/web/{entity}.test.tsx |
bun:test + HappyDOM |
More from schema0/skills
schema0-dev
>-
23schema0-mobile
Mobile platform patterns — React Native / Expo, worker architecture, ORPC client, and navigation
17schema0-rls
Row-level security setup — RLS policies, authenticated database connections, and user-scoped data access
17schema0-ai
AI SDK integration with ORPC — chat streaming, prompt-response, tool calling, and provider configuration
17schema0-web-crud
Web frontend CRUD features — query collections, table columns, dialogs, forms, views, sidebar, and orchestration
17schema0-cli
CLI commands for sandbox execution, deployment, version management, secrets, and third-party integrations
17