Run it once, run it ten thousand times, run it with five hundred users.
The runner walks a project or a folder with a dataset and writes a report. The Runner view turns a request into a form for the people who send but do not edit. The load test puts up to 500 virtual users on it, from this computer or from servers you reach over SSH, and keeps the numbers.
At a glance
A row becomes a send. A request becomes a form. Five hundred users become numbers.
The runner takes a project or a folder in order and a dataset beside it — CSV with a header row, TSV or a JSON array, up to 10,000 rows — and sends once per row with the row's columns as variables, honouring what the scripts say with setNextRequest and skipRequest, then writes a report in HTML, JUnit XML or JSON. The Runner view is the same request seen by someone whose permission is Send and run: every row of it hidden, shown, or filled by the person, with the scripts and checks running on what they send.
The load test is up to 500 virtual users on the same requests, from this computer or from servers reached over SSH, with the numbers live while it runs and kept when it ends — on this computer only, never published to the team.
Via, the SSH originsPick it, feed it, run it, read it.
A run is a project or a folder, a dataset, a few settings and a report — nothing to script unless you want to.
Pick
A project or a folder, walked in order. Untick the requests to leave out. A script's setNextRequest and skipRequest are honoured, so a run can branch and skip the way a send does.
Feed
CSV with a header row, TSV, or a JSON array — up to 10,000 rows. One iteration per row, each row's columns as variables, the data-file row second only to what a script set.
Run
Iterations 1 to 10,000. A delay between sends. Stop at the first failure, or run through and count.
Read
A report in HTML, JUnit XML or JSON, written when the run ends: every request, every check, every iteration.
A request becomes a form.
For the people whose permission is Send and run: every row of a request set to hidden, shown, or "the runner fills it".
Per row: hidden, shown, or the runner fills it.
The address, a path variable, a parameter, a header, a body field, the auth — each one hidden, shown, or filled by the person. Auth is hidden from runners by default.
Set once, inherited down.
Set on a request, a folder or a project, and inherited down. "Words for the runner" puts instructions above the form. Preview the request as a runner sees it.
Still checked.
Scripts and checks run on what the runner sends. Without a Runner view, a runner sends a scratch copy that is never saved.
The numbers a load test has to give you.
Up to 500 users, by duration or by count, a ramp-up of up to 600 seconds and a think time between sends. Live while it runs: requests per second, latency per second as p50, p95, p99 and max, status classes per second, a latency histogram, KB/s and requests in flight — per request and per origin. Kept when it ends, read against the targets you set for Apdex, p95, error rate and minimum req/s, and compared two at a time.
Beside it, a run two minutes in, and the verdict at its end.