verify-test-coverage

To check for missing test files for custom hooks and utilities, run a verification process that scans for corresponding .test.ts or .test.tsx files in designated directories. This ensures every source file has matching test coverage to prevent regressions.

To find orphan test files that no longer have corresponding source code, run an orphan test detection check. This process identifies and reports .test.ts or .test.tsx files in your test directories that lack matching source implementations.

To enforce JSX test file extension rules in a vitest project, apply an extension rule validation check that ensures any test file using JSX syntax correctly uses the .test.tsx extension instead of .test.ts.

Verifying test coverage for hooks requires designated test directories containing .test.ts or .test.tsx files. The verification process scans these specific locations to match test files with their corresponding custom hook and utility source files.

Test coverage verification works for utility functions that don't use JSX by checking for the existence of corresponding .test.ts files. It validates standard TypeScript test files alongside enforcing .test.tsx rules for files containing JSX syntax.

You should run a test file existence check after adding a new custom hook or utility function to your codebase. This confirms you have created the corresponding test file immediately, maintaining code quality and preventing regressions.