If you’re using Postman to test Web API functionality, and want to generate a load test from the API call collections you have, you should opt for a specialized load testing tool such as LoadView.

LoadView supports the import of a Postman Collection from the file or the shared link to create a Postman load test. To test API behavior under the user load, the collection of requests will be repeatedly executed by the specified number of virtual users during the test duration time.  The conditions that were specified for the requests in Postman are used to verify API responses. If any condition is not met during a load test session, the session will be marked as failed.

To start with load testing, you need to have an active LoadView account.

Creating a Load Test Script

Once logged in to LoadView, create a Postman Collection task to upload a collection of the HTTP requests from Postman to LoadView and configure the test script parameters.

The system supports test scripts with a duration of up to 30 seconds. Make sure the collection of the Postman requests does not exceed the limit.

Configuring a Load Test Scenario

Once the task has been created, you will be prompted to configure the load test scenario. For a detailed guide on scenario setup, see Getting Started with Load Test Setup. In this section, we will discuss some of the characteristics related to load testing with Postman Collections.

User Behavior Profile

If you need to execute the load test script with a custom delay between runs, adjust user behavior settings. For example, if you need a virtual user to wait from 10 to 20 seconds before the next script run, select the Custom mode and specify the range in the corresponding fields.

Load Injector Payload

The system calculates optimal payload during device calibration. It is highly recommended to stick to the suggested payload value.

If it is required, you can also set up a custom payload from 20 to 100 users per Load Injector Server.

To scale up a large number of concurrent users, please consider creating the multi-task REST WEB API load test using the Postman collection of calls.