Creating a Test
Creating a New Test #
Click on that big green "New Test" button to get started.
You should see a form like this for creating your new test:
Test Name #
Test Type #
Clients & Duration #
- Clients per test: there is just one field: "Connections". Whatever number you enter here is the number of connections that will be made to your server over the duration of the test
- Clients per second: there is just one field: "Connections". Whatever number you enter here is the number of connections that will be made to your server per second
- Maintain client load: there is a "from" and a "to" field. The test starts with some number of connections ("from") and can increase the connections throughout the test, reaching the number in the "to" field by the end of the test.
Notes & Tags #
Advanced Settings #
To customize the error threshold, timeout values, or add basic authentication to your test, click the "Advanced settings" button to expand these options.
Be careful with this!! Authentication details are stored unencrypted on our servers, because if we encrypted them, we wouldn't be able to use them during the test. We recommend creating a test user for use with loader.io if you need to test against an authenticated server.
Timeout & Error (%) #
URLs & Options #
- HTTP Headers: if your app needs special HTTP headers to be sent, you can specify them here. The header name (e.g.
Content-Type) goes in the left box, and the value (e.g.
application/json) in the right box. Click the "+" button to add more.
- Request Parameters: You can add key/value pairs in these input boxes, and they will be URL-encoded and added to the query string of your URL if the request type is GET or DELETE, or URL-encoded and added to the request body for POST, PUT, or PATCH requests
- Payload File: You can use a specially-formatted JSON file to pass varying data on each request. Craft your payload file, put it at a public URL, and enter that URL in the box labeled "Payload file URL", within the "Parameters" section. When you run the test, loader.io will download the file, parse it, and use the data in the request body. See payload files for more details on the format.
- Raw Body: If you are POSTing, PUTing, or PATCHing data that is not URL-encoded (e.g. json or other formats), use the "Raw Body" input. Don't forget to add a "Content-Type" header if needed.
- Response Variables: You can define variables that are associated with HTTP response header fields, and use these variables in other URLs and options. See variables for more details on how to use variables in your tests.