LoadLitmus is the dashboard we run our performance tests from. It wraps JMeter in a browser UI: pick a plan, set the load, press play, watch the log stream, and keep every run's results in one place per project. It runs on your own machine or a test server — no cloud, no database, all data stays local.
Important: this track is written against LoadLitmus 1.4.5 with JMeter 5.6.3, and covers the parts we use on real engagements. Everything in the Status table below was exercised on a live instance while writing; anything not exercised says so.
Status
| Page | Status | Notes |
|---|
| 1. What LoadLitmus Is | Reviewed | Conceptual page |
| 2. Install and First Project | Partly validated | Dev install (python -m webapp) and project creation run on macOS. Windows installer and .deb not re-tested for this guide |
| 2a. Getting Around | Validated | Every sidebar page captured from 1.4.5 with a demo project |
| 3. Script Requirements | Validated | Every rule checked against six real project scripts and against LoadLitmus's own load reader |
| 4. Running a Test | Validated | Four runs executed from the UI against a local stub app |
| 5. Results and Monitoring | Partly validated | Results, reports and auto-analysis exercised. InfluxDB monitoring described from configuration, not run for this guide |
| 6. Fleet and Distributed Runs | Not yet validated | Written from the app's behaviour and our past distributed projects; no fleet was provisioned while writing |
| Appendix. Starter Template | Validated | The template ships with this guide and was run end to end. Test Editor is beta with known bugs. |
Basics
Running Tests
| # | Topic | Description |
|---|
| 4 | Running a Test | The Runner page, load, parameters, test data, stopping, CI |
| 5 | Results and Monitoring | Reading runs, reports, comparisons, live monitoring |
| 6 | Fleet and Distributed Runs | Slave machines, provisioning, distributing data |
Appendix
Where this sits