frontend-testing

To automate Vitest and React Testing Library tests, analyze the target file with pnpm analyze-component, then generate and run the corresponding test file using provided templates before proceeding to the next file.

The best way to write integration tests for multi-file frontend projects is using incremental testing guidance with templates, ensuring real project components are used and specific mock patterns are enforced for reliable suites.

Yes, this frontend testing approach supports both unit and integration tests, enforcing testing conventions from documentation to maximize coverage and consistency across hooks, utilities, and components.

Yes, you can use this to enforce testing best practices by adhering to conventions from web/testing/testing.md, which guides incremental development and requires specific mock patterns for maintainable test suites.

Frontend component tests fail without specific mock patterns because the workflow requires them to ensure reliable, maintainable test suites, preventing inconsistencies when testing hooks and utilities.

You need coverage-focused tests for frontend hooks and utilities when maximizing test coverage and consistency across a multi-file project, ensuring reliable behavior through enforced testing conventions.