testing-strategy

Structure TypeScript tests by separating unit (*.test.ts) and integration (*.test.int.ts) files to enforce a reliable test pyramid. This naming convention guides the testing workflow and keeps integration tests isolated from unit tests.

Mock dependencies in Vitest by combining dependency injection with vitest-mock-extended. This pattern provides fully typed, deterministic mocks that isolate units of code and ensure reliable, repeatable test execution.

Faker integrates into the TypeScript testing workflow to generate realistic fake data for unit and integration tests. It replaces static mock data, ensuring test inputs mimic real-world scenarios while maintaining deterministic test behavior.

Yes, you can run k6 load tests alongside Vitest by placing k6 scripts in a dedicated load/ directory. This isolates load testing workflows from unit and integration tests while maintaining a unified testing strategy.

Prevent integration tests from running in non-local environments by adding a vitest.setup.ts file. This setup file enforces guardrails, ensuring integration tests only execute locally and protecting external environments from accidental test data.

Use dependency injection for TypeScript unit testing to enable isolated, deterministic tests with typed mocks. This pattern solves unreliable ad-hoc testing by allowing precise control over dependencies via vitest-mock-extended.