frontend-testing

To generate Vitest and React Testing Library tests, provide the component path to trigger automated spec file generation. The skill outputs tests covering components, hooks, and utilities following the AAA pattern and black-box testing conventions.

Writing frontend tests for React hooks and utilities is streamlined by generating Vitest spec files automatically. The skill enforces semantic naming conventions and black-box testing to ensure robust component behavior and reliable hook execution.

Yes, you can perform coverage analysis on existing React Testing Library spec files. The skill supports coverage analysis triggers to evaluate test effectiveness for your frontend codebase, identifying untested components and utility branches.

The generated Vitest test code strictly adheres to frontend testing conventions, including the AAA pattern, black-box testing principles, and semantic file naming. It ensures tests align with specific tech stack versions and project requirements.

You should not use automated test generation when your frontend components require highly custom integration tests external to the React Testing Library ecosystem. The skill focuses on Vitest, component hooks, and utility testing rather than end-to-end browser automation.