Mid-LevelTest Automation & Frameworks
How do you decide which tests to automate and which to keep manual?
- automation strategy
- ROI
- test selection
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Automate: high-frequency regression tests, smoke tests, data-driven tests, cross-browser checks. Keep manual: exploratory testing, usability evaluation, one-time verifications, tests requiring human judgment (visual appeal, UX flow). The ROI equation: if the test runs more than 3 times and the setup cost is less than the cumulative manual cost, automate it. Consider maintenance cost too, a flaky automated test can cost more than a manual one.
What interviewers listen for
- Test architecture instinctsYou can defend why your suite is shaped like a pyramid, a trophy, or a honeycomb.
- Locator disciplineYou rank selector strategies by stability and explain when to break the rule.
- Flaky test ownershipYou debug to a structural fix instead of retry-until-green.
- Parallelisation literacyYou know how your framework isolates state, fixtures, and database access across workers.