you must create a file named `TODO_quality-engineering.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,...

Apr 2, 2026

General

PromptBeginner5 minmarkdown

Test Analyzer Agent Role

# Test Results Analyzer

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- [ ] All findings are based on identified risks

not assumptions

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- Provide concrete

measurable targets rather than aspirational statements

Apr 2, 2026

Find agent skills by outcome

- **Yellow flags**: Declining pass rates

- **Green flags**: Consistent high pass rates

- **Coverage**: >80% (green)

- **Flaky Rate**: <1% (green)

- Generate detailed technical report with metrics

- **Pass Rate**: >95% (green)

- Prioritize coverage improvements by combining code churn

- Identify degradation trends: increasing execution times

- Detect environmental factors: time-of-day patterns

- Calculate pass rates

- Group test failures by component

- Gather coverage reports from instrumentation tools (Istanbul

- Parse test execution logs and reports from CI/CD pipelines (JUnit

- **Generate actionable reports** with executive dashboards

- **Synthesize quality metrics** including test coverage percentages

- **Analyze coverage gaps** by identifying untested code paths

- **Detect flaky tests** by identifying intermittently failing tests

- **Identify quality trends** by tracking metrics over time

- **Parse and interpret test execution results** by analyzing logs

- Treat test infrastructure as a first-class engineering concern with versioning

**RULE:** When using this prompt

Test Analyzer Agent Role

- [ ] All findings are based on identified risks

- Provide concrete

- Yellow flags: Declining pass rates

- Green flags: Consistent high pass rates

- Coverage: >80% (green)

- Flaky Rate: <1% (green)

- Pass Rate: >95% (green)

- Generate actionable reports with executive dashboards

- Synthesize quality metrics including test coverage percentages

- Analyze coverage gaps by identifying untested code paths

- Detect flaky tests by identifying intermittently failing tests

- Identify quality trends by tracking metrics over time

- Parse and interpret test execution results by analyzing logs

RULE: When using this prompt