Mid-LevelCI/CD & DevOps for QA
What is shift-left testing and how do you implement it?
- shift-left
- early testing
- prevention
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Shift-left means moving testing earlier in the development lifecycle, finding bugs when they're cheapest to fix. Implementation: (1) Pre-commit - linting, type checking, unit tests. (2) PR-level - automated test suite, code review with testability focus. (3) Design phase - QA reviews designs and writes test scenarios before development starts. (4) Requirements - QA participates in story grooming, identifies edge cases. (5) Developer testing - encourage developers to write tests, provide easy-to-use test infrastructure. The goal: bugs found in code review, not in production.
What interviewers listen for
- Pipeline shapeYou design stages by failure cost and runtime budget, not by tool feature lists.
- Parallelisation craftYou can shard a real suite and explain the state-isolation choices you made.
- Quality gatesYou know which checks block merge, which warn, and why those defaults are correct.
- Shift-left fluencyYou talk about ownership transfer, not just earlier execution.