PrincipalCI/CD & DevOps for QA
How do you implement chaos engineering in a CI/CD pipeline?
- chaos engineering
- resilience
- fault injection
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Chaos engineering deliberately injects failures to test resilience. CI integration: (1) Start with game days, manual experiments in staging. (2) Automate with tools (Chaos Monkey, Litmus, Gremlin) - kill pods, inject latency, simulate network partitions. (3) Define steady-state metrics - error rate, response time, throughput. (4) Run experiments and verify the system stays within acceptable bounds. (5) Graduate to production chaos (carefully, with kill switches). QA role: define the "blast radius," monitor impact, and validate self-healing. Start small - kill one instance and verify recovery.
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.