Mid-LevelQA Methodology & Strategy
How do you approach regression testing effectively?
- regression testing
- test maintenance
- automation
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Regression testing verifies that new changes don't break existing functionality. Strategy: (1) Automate the regression suite, no human should repeatedly run the same tests. (2) Prioritize by risk - not every test runs on every change. (3) Maintain the suite - remove obsolete tests, update for UI changes, fix flaky tests. (4) Layer it - smoke tests (5 minutes) on every commit, full regression (30 minutes) on PR merge, extended regression (hours) nightly. The biggest antipattern: a regression suite that takes so long nobody runs it.
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.