/ SONDA · BUILD

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.

Every line in the list Via, the SSH origins
10,000 ITERATIONS CSV · TSV · JSON DATASETS HTML · JUNIT · JSON 500 VIRTUAL USERS

At a glance

RunnerA project or a folder, in order; untick requests; iterations 1 to 10,000; a delay; stop at the first failure; setNextRequest and skipRequest honoured.
DataCSV with a header row, TSV, or a JSON array — up to 10,000 rows, one iteration per row, each row's columns as variables.
ReportsHTML, JUnit XML, JSON.
LoadUp to 500 users, by duration or by count, ramp-up to 600 s, think time; targets for Apdex, p95, error rate and minimum req/s.
KeptTwenty load reports per item, on this computer only — never published to the team.
/ THE RUNNER VIEW

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

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.

Inherited

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.

/ LOAD

The numbers a load test has to give you.

Live while it runs, kept when it ends, compared two at a time.

Live

Requests per second, latency per second as p50, p95, p99 and max, status classes per second, a latency histogram, KB/s, requests in flight — per request and per origin. Histogram steps of 1 ms under 100 ms, 10 ms to a second, 100 ms to ten.

Origins

Local, plus any SSH tunnel: the users run from those servers, and a tunnel origin's timing includes the hop. Failed checks can count as failures.

After

Pass criteria read against the targets. Twenty runs kept, two compared side by side. Export HTML with the charts drawn in, JUnit or JSON. "Explain this run" hands the numbers to Themis.

/ LOCKFLARE SONDA

The runner and the load test, in the free edition.

Load testing, listed →