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.
Running load from several machines with LoadLitmus Fleet - slaves over SSH, provisioning, ports, distributing test data and collecting failed responses.
A practical guide to LoadLitmus, the on-premise web dashboard we use to run, store and report JMeter performance tests.
How to run smoke, load, stress, endurance, spike and scalability tests from one JMeter test plan.
What performance testing is, where it sits in the testing family, and how load, stress, spike, endurance and scalability tests differ.
How a performance engagement runs end to end, from client requirements to a signed-off report, with the tester's part in each phase.
The Pizza Playground, a Docker-based pizza ordering app we use as the target for JMeter, k6 and Playwright practice.
The Runner page end to end - selecting a plan, setting load, parameters and data, watching the live log, stopping safely, and copying the run into CI.
What a JMeter .jmx file needs so LoadLitmus can drive its load, data and results - and which thread-group shapes turn features off.
A ready-made JMeter .jmx skeleton built for LoadLitmus - download it, fill in the placeholders, and start a project with the Load card, guards and portable paths already wired up.
Accounts, reset, load-test switches, UI test ids and the API map for the Pizza Playground.
What the LoadLitmus dashboard does, what it deliberately does not do, and when to use it instead of running JMeter by hand.