How do you integrate performance testing into a CI/CD pipeline?
- CI/CD integration
- automation
- performance gates
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Approach: (1) Lightweight smoke performance tests on every PR (5-10 seconds, verify no major regression). (2) Full performance suite on merge to main or nightly (realistic load, 5-30 minutes). (3) Threshold-based gates: fail the build if p95 > SLA or error rate > 1%. (4) Trend tracking: store results over time, alert on gradual degradation. (5) Isolated test environment that mirrors production. (6) Parameterized tests: different profiles for smoke vs full load. Tools: k6 with GitHub Actions, Gatling with Jenkins, custom scripts with threshold assertions.
What interviewers listen for
- Workload modellingYou design the load shape from product traffic, not from tool defaults.
- Percentile literacyYou read p50/p95/p99 separately and explain why each matters.
- Bottleneck triageYou correlate metrics across application, database, and infrastructure layers.
- Capacity instinctsYou can translate a soak test into a sizing or scaling recommendation.