testing-patterns

Structure Vitest unit tests in a TypeScript monorepo by co-locating test files alongside source code, applying clear naming conventions, and utilizing shared fixtures to ensure consistency and readability. This simplifies navigation and refactoring.

The best Vitest conventions for organizing test fixtures involve defining shared fixtures centrally and co-locating tests with source files. This standardizes testing practices, improves reliability, and maintains readability across monorepo projects.

Yes, you can use these Vitest testing patterns for integration tests. The conventions standardize both unit and integration testing by defining file naming, test structure, fixture usage, and Vitest setup for TypeScript projects.

You should co-locate test files with source files in Vitest to simplify navigation and refactoring. This testing structure ensures developers can quickly find and update tests alongside related code, improving overall maintainability.

Yes, this skill defines Vitest setup and configuration standards. It codifies specific conventions for file naming, test structure, fixture usage, and setup that developers must follow to standardize testing practices across projects.