risk-based-testing

The risk-based-testing skill provides an intelligent, data-driven framework for engineering teams to focus their quality assurance efforts on the areas of the codebase where failure carries the highest impact. By moving away from uniform test coverage toward a risk-weighted strategy, teams can significantly optimize CI/CD pipelines, reduce execution times, and improve overall product stability. This skill is designed for Quality Engineers, DevOps practitioners, and Lead Developers who need to balance development speed with rigorous system verification.

• Automatically scores components on a 1-5 scale for both impact and probability, generating a priority matrix ranging from Low to Critical.

• Integrates with regression-testing and shift-right-testing strategies to dynamically adjust risk scores based on production incidents, historical bug frequency, and code churn metrics.

• Orchestrates a specialized fleet of agents, including the qe-regression-risk-analyzer and qe-test-generator, to dynamically map test depth to the calculated risk level.

• Implements sophisticated effort allocation logic, recommending 60% of resources for Critical features and ensuring high-risk areas receive comprehensive integration, performance, and security testing.

• Provides seamless integration with CI/CD platforms, enabling conditional test execution so that only risk-relevant tests are triggered during pull request cycles, drastically reducing build times and AI token consumption.

• Leverages ML-driven predictive analytics, using models like gradient boosting to analyze historical bug patterns, author experience, and file complexity to anticipate where future defects are likely to surface.

• Utilize this skill during sprint planning to determine the scope of automated testing for new feature releases.

• Use the provided TypeScript task templates to define test depth requirements for specific application modules, such as payment gateways or authentication services.

• Configure CI/CD pipelines to read risk-score outputs and selectively skip tests in low-risk files to streamline local development and server-side validation.

• Maintain dynamic risk profiles by feeding production monitoring data back into the system via the qe-production-intelligence agent to ensure that tests evolve alongside the stability of the production environment.

• Observe the namespace structure aqe/risk-based/ to track evolving risk scores, coverage maps, and historical incident patterns across multiple projects.