Skip to main content

Performance testing playbook

Performance verified against budgets in CI, run risk-based — not a heroic load test the week before launch.

The method​

  • Workload modelling — realistic traffic shapes for the product (peak renewals, claims surges).
  • SLOs & performance budgets — p95/p99 latency and throughput targets, set at Definition (NFR catalogue).
  • Budgets enforced in CI — k6 / Gatling per the radar; a regression past budget fails the build.
  • Baseline-and-trend — track performance over time, not just pass/fail.

Risk-based​

Not every change needs a load test. A rule decides when it's warranted — a change to a hot path, a new query, a scaling-sensitive feature. This keeps the Refinement performance pass proportionate: rigorous where it matters, skipped where it doesn't.

Standards referenced: ISO/IEC 25010, SRE SLOs.