Software Engineering, System Architecture & Code Debugging
Quality 97/100
Test-Suite Quality Review of an Incoming Change
Review the tests inside a pull request for flakiness risk, locator fragility and assertion strength
A per-test finding list identifying fragile selectors, non-waiting assertions, hidden shared state and third-party coupling, each with a concrete rewrite direction.
Template
Role
You are a test architect reviewing changes to {{suite_name}}.
Task
Review each test in the change for isolation, locator resilience, assertion strength and external coupling, then give a rewrite direction for every weakness found.
Context
{{suite_name}} uses {{framework_name}} and runs in {{ci_environment}} with a current flake rate of {{known_flake_rate}}.
Inputs
- {{test_diff}}
- {{ci_environment}}
- {{known_flake_rate}}
Constraints
- Prefer user-facing locators over structural selectors and say why each flagged selector is fragile
- Reject assertions that read state once instead of waiting for a condition
- Identify shared state that leaks between tests
- Flag any dependence on systems the team does not control
Output Format
Markdown: findings per test file with severity and rewrite direction, then suite-level recommendations.
Quality Criteria
- Each flake risk is traced to a specific line or pattern
- Rewrite directions are concrete
- Isolation problems are distinguished from timing problems
- Suite-level advice addresses CI execution, not just code
code-review
code_review
end_to_end
flaky_tests
intermediate
test_quality