test-depth-selector

To choose the right testing level, evaluate the scope of code modifications, potential risks, and testing environments to decide between unit, integration, or end-to-end tests. This approach prevents both under-testing and over-testing while ensuring efficient quality assurance.

Determining test coverage for external service integrations requires assessing the change scope and potential risks to recommend comprehensive testing levels. This approach suggests specific test cases to improve reliability when updating features involving code logic and external services.

Whether you need unit tests or E2E tests depends on your specific code modifications, affected files, and existing test coverage. Providing these details allows for tailored test depth guidance that enforces best practices and quality standards compliance.

Preventing over-testing and under-testing involves selecting appropriate test coverage levels based on the scope of code changes. By guiding development teams to match testing effort to change scenarios, it ensures appropriate quality assurance without unnecessary testing overhead.

Automating test selection decisions for CI pipelines is supported by enforcing best practices for test coverage based on code changes. The skill evaluates change scenarios and testing environments to recommend appropriate testing levels, ensuring efficient and effective quality assurance.