test-runner

Running unit and integration tests in CI is automated by detecting Vitest or Jest configurations and executing targeted test patterns. This skill generates readable outcome reports and can re-run failed tests directly within your workflow.

Yes, framework detection automatically identifies Vitest or Jest configurations in your project. It routes commands to the appropriate test runner, ensuring the correct suite executes without requiring manual framework specification.

Yes, flexible targeting supports running tests by specific patterns, allowing you to isolate unit or integration tests. You can execute individual patterns or all tests without modifying your underlying configuration files.

The best way to execute unit tests locally is to run a single command targeting unit test patterns. The skill handles framework detection and displays readable test results and coverage options for your JavaScript or TypeScript project.

You can re-run failed tests using the outcome reporting feature, which assesses initial test results and targets only the failed cases. This prevents re-executing successful tests and speeds up your feedback loop.

The limitation of using a Bash script is that test execution is constrained to environments supporting Bash and standard command-line routing. Complex custom runner configurations or non-CLI framework integrations may not be fully supported by this approach.