target-testslisted

# Target Tests Identify the highest-value targets for additional test coverage by combining risk, complexity, and behavioral signals. ## Prerequisites Omen CLI must be installed and available in PATH. ## Workflow ### Step 1: Identify High-Risk Files Run the defect prediction analysis: ```bash omen -f json defect ``` Files with high defect probability are statistically likely to contain bugs. ### Step 2: Find Hotspots Run the hotspot analysis: ```bash omen -f json hotspot ``` High-churn + high-complexity code needs regression protection. ### Step 3: Analyze Complexity Run the complexity analysis: ```bash omen -f json complexity ``` Complex functions have many code paths that need coverage. ### Step 4: Check Ownership Run the ownership analysis: ```bash omen -f json ownership ``` Single-owner code needs tests as documentation for when others maintain it. ## Test Priority Matrix Prioritize based on combined signals: | Priority | Signals | Why Test | |----------|---------|----------| | Critical | High risk + High complexity + High churn | Bugs likely, changes often, hard to verify | | High | High complexity + Single owner | Many paths, tests = documentation | | Medium | High churn + Moderate complexity | Changes often, needs regression protection | | Lower | Low complexity + Low churn | Stable, simple code | ## Test Case Estimation Use cyclomatic complexity to estimate test cases needed: | Cyclomatic Complexity | Minimum Test Cases | |-------------------