What problem does it solve?
Provides a single, consistent testing convention for Peek to eliminate flaky tests, unclear mocking patterns, and inconsistent coverage between client, server, and E2E suites so teams can write reliable, maintainable tests.
Core Features & Use Cases
- Client unit testing: Conventions for Vitest 3.x with React Testing Library, user-event, happy-dom, test file locations, query priorities, and rendering helpers.
- Server unit & integration testing: Patterns for mocking Prisma, enforcing sequential execution for DB-sensitive tests, and running integration tests against a dedicated Stash test instance using STASH_TEST_URL and STASH_TEST_API_KEY.
- E2E with Playwright: Centralized Playwright conventions, storage-state auth setup, CI and local run instructions, and locator/assertion priorities to avoid brittle tests.
- CI & quality gates: Coverage thresholds and command patterns to run client, server, integration, and E2E suites reliably.
Quick Start
Run the client tests by executing the project's Vitest command in the client directory and follow the documented naming, mocking, and query-priority conventions.