Architecture
What the Pizza Playground is made of, how one order flows through its four containers, and what that means for UI and load testing.
What the Pizza Playground is made of, how one order flows through its four containers, and what that means for UI and load testing.
Logging in, correlating ids between requests, and shared test data with SharedArray.
Pass/fail criteria inside a k6 script.
Making a failing k6 script tell you why.
Running k6 scripts and reading the summary and output.
Grafana Cloud output, the browser module, xk6 extensions.
Get k6 installed and run the first script against the Pizza Playground.
The k6 lifecycle, VUs vs. iterations, how options/CLI/env vars stack, and a JMeter-to-k6 cheat sheet.
Stages, executors and profiles from the Performance Testing module, in k6.
A practical, developer-centric approach to load testing the Pizza Playground with k6.
How to run smoke, load, stress, endurance, spike and scalability tests from one k6 script.
The Pizza Playground, a Docker-based pizza ordering app we use as the target for JMeter, k6 and Playwright practice.
Recording a HAR with Playwright codegen or DevTools, turning it into a k6 script with har-to-k6, and why a green replay can still be wrong.
Communicating k6 findings.
Download the runnable k6 sample, what is inside it, and the command and -e switches for each script.
Accounts, reset, load-test switches, UI test ids and the API map for the Pizza Playground.
The questions to ask before scripting are tool-neutral; here is how the answers translate into k6.
Send k6 results to Prometheus, put them on one Grafana dashboard next to the server, and read cause and effect during a load test.