5 / 6
k6 load testing

Analyze results and report findings

Hard120 pts~45 min
  • Reporting
  • Result analysis
Practice app · Checkout Service

A load-testable checkout service with realistic latency that degrades under concurrency, plus a live metrics view.

BASE_URL
/api/practice
Console app
/lab/performance-testing-analyze-results-and-report-findings

Your starter code already declares BASE_URL — call the API relative to it.

Objective

Run a baseline, collect the service metrics and print a concise findings report.

Your task

  1. 1Set options { vus: 5, iterations: 40 } with a p95 threshold.
  2. 2GET BASE_URL + "/perf/checkout" and GET BASE_URL + "/perf/search?q=mug" with checks.
  3. 3Every 4th iteration of a VU (__ITER % 4 === 3) also GET BASE_URL + "/perf/metrics".
  4. 4console.log a report: rps, p95, errorRate, slowest recent path, and PASS/FAIL against the SLO.

Acceptance criteria

  • Checkout, search and metrics return 200
  • A findings report is logged
  • ≥ 60 requests are sent
  • At least 60 check() calls pass

k6 load testing · Performance Testing · Scaling & analysis