ML Test Selection
Quick Reference
What & Why
Definition
>= 80% of PRs run only affected tests (ML predicts impact) reducing test time by >= 70% while maintaining 99% defect detection.
Business Value
Generates 70% of test cases automatically with 90% assertion quality and discovers 3x more edge cases through AI-powered test generation Achieving >= 70% test time reduction, 99% defect detection is a key milestone toward this goal.
Context
This capability is part of the Optimization milestone's focus on ai enablement, predictive ops, self-healing. Essential for teams targeting CFR, LT improvements.
Success Criteria
Target
>= 70% test time reduction, 99% defect detection
Measurement
Test selection accuracy + time savings + missed defects
Evidence
- Test impact analysis model
- Test selection metrics
- Escaped defect analysis
In Practice
Real-World Implementation
ML analyzes code changes, traces impact through call graph, selects affected tests. Runs 30% of tests, catches 99% of defects, 70% time savings.
Concrete Example
Implementation Guide
Prerequisites
Implementation Steps
Follow the measurement approach: Test selection accuracy + time savings + missed defects
For detailed step-by-step guidance, refer to the AI-Generated Testing & Intelligent Quality Implementation Kit.
Resources
Implementation Kit
AI-Generated Testing & Intelligent Quality KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Prerequisites
Implement these first
Complementary
Often adopted together, from the AI-Generated Testing & Intelligent Quality epic
Troubleshooting & FAQs
Common Issues
Issue: Target metric not improving
Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness
Issue: Team resistance to adoption
Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition
Issue: Inconsistent implementation across teams
Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards
Frequently Asked Questions
Can we implement this before completing prerequisites?
While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.
How long does implementation typically take?
Most capabilities can be implemented within 185 days when tackled as part of the Optimization milestone. Individual timelines vary based on team size and existing practices.