SeniorCI/CD & DevOps for QA
What is GitOps and how does it affect testing workflows?
- GitOps
- ArgoCD
- version control
Answer it first, then compare. Nothing here is saved or scored.
Model answer
GitOps treats Git as the single source of truth for infrastructure and application state, changes are made via PRs, applied by automated operators (ArgoCD, Flux). For testing: (1) Every environment change is a code change, so it's testable in CI. (2) Rollback is a git revert. (3) Environment drift is eliminated - if it's not in Git, it's not deployed. (4) Test configurations are versioned alongside code. QA benefit: you can reproduce any environment state by checking out that commit.
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.