create-unit-test

To create Vitest unit tests matching project patterns, use a template-driven approach that co-locates test files next to source files. This ensures consistency by applying standard structures for components, models, and route loaders using built-in mocking strategies.

Co-locating test files involves placing the test file directly next to its source file, such as creating Button.test.tsx alongside Button.tsx. This pattern keeps tests organized and easily discoverable within your project structure.

The best way to mock dependencies in Vitest for route loaders and actions is to apply standard mocking patterns that isolate your modules. This ensures tests run reliably by replacing external dependencies with controlled mock implementations.

Yes, you need Vitest already set up in your project along with TypeScript support. This setup is required to generate and run the standard test templates for your functions, components, models, and route loaders.

Standard Vitest templates are available for testing functions, components, models, and route loaders. These templates provide a ready-to-run describe/it/test structure, ensuring consistent testing patterns across your entire codebase.

Co-located tests place files like Button.test.tsx next to Button.tsx to improve maintainability. This pattern ensures tests are immediately accessible during development, reducing context switching compared to using a separate test directory.