Section 4 · Complete your k6 performance testing journey

Wrap-up transition recapping the baseline module and previewing the transfer exercise and resources

Estimated time: 1 min

Journey wrap-up

What you learned in Module 3:

How to design a load profile with stages
How to write checks for per-response correctness
How to set thresholds from what you measured (not from guesses)
How a baseline run produces a deliberate pass or fail verdict

What you’ll do in this module:

Transfer exercise: Apply the QuickPizza pattern to a service your team owns
Where to go next: Stress, spike, soak, and reference docs

Estimated time: 5 minutes for wrap-up content; 15-30 minutes for the transfer exercise

0:00

Read transcript

Audio transcript

You’ve completed both modules. Take a moment to appreciate how far you’ve come.

In Module 2, you installed k6, wrote a test script, ran it locally, and sent results to Grafana Cloud. You went from zero to a working performance test.

In Module 3, you took those raw results and turned them into something actionable. You designed a realistic load profile, added checks for correctness, and set thresholds that make your test pass or fail automatically.

Together, you’ve built a repeatable, automated performance test that validates your system against a known baseline. This test can run during development for quick feedback, in continuous integration and deployment pipelines to catch regressions before they ship, or on a schedule to detect infrastructure-level changes.

Your baseline answers the most important question in performance testing: what does normal look like? Every advanced testing technique builds on that answer.

Journey wrap-up

Still have questions?

Get every update