Mid-LevelQA Methodology & Strategy
How do you approach regression testing in an agile team?
- regression testing
- agile
- automation
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Strategy: (1) Automate regression tests for core flows, run on every PR. (2) Risk-based selection: focus on areas affected by the current sprint changes. (3) Maintain a lightweight regression checklist for manual spot-checks. (4) Expand automation each sprint: the new feature test becomes next sprint's regression test. (5) Full regression before major releases (automated). (6) Exploratory regression: time-boxed sessions around changed areas. Key: regression testing should not be a bottleneck. If it takes more than 1 hour, automate more.
What interviewers listen for
- Risk-based prioritisationYou can defend skipping coverage on a path because the risk maths supports it.
- Test design fluencyYou apply equivalence partitioning and decision tables to concrete inputs in real time.
- Metric judgmentYou distinguish between metrics that drive learning and metrics that drive theatre.
- Strategy under constraintYou can produce a defensible plan when the team has half the time and twice the scope.