Mid-LevelTest Automation & Frameworks
What is the test automation pyramid and do you agree with it?
- test pyramid
- test strategy
- architecture
Answer it first, then compare. Nothing here is saved or scored.
Model answer
The pyramid suggests: many unit tests (fast, cheap), fewer integration tests, and few E2E/UI tests (slow, expensive). It's a useful heuristic but not absolute. Modern alternatives: the "testing trophy" emphasizes integration tests as the sweet spot. For QA-led automation, focus on where you add the most value, often API integration tests and critical E2E paths. The anti-pattern is an "ice cream cone", heavy E2E, few unit tests - which is slow and fragile.
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.