If you have been using Postman to test Web API performance, the Postman Collection Task can be a very fast and effective tool to set up a load test in LoadView. To start with configuring a load test, all you have to do is create a Collection from the existed Web API calls in Postman and upload it to Dotcom-Monitor.
When to choose the HTTP Task instead of the Postman Collection Task
There is an aspect you need to consider upon configuring a load test using a Postman Collection. In LoadView, each script of a Postman test is executed by a dedicated process. Due to particularities in load allocation on the Load Injector Servers, LoadView can execute up to 30 processes at a time on a single Load Injector Server. So you can set up the system to run up to 30 concurrent users per Load Injector. In terms of payload it means that the more concurrent users you want to run while testing the more Load Injectors you need to use for the load test. This can increase the overall cost for large load tests (see Load Injector Pricing).
In the case when you need to scale up a large number of concurrent users, please consider converting the Postman Collection to the multi-request HTTP load test as described for Rest Web API load testing. Since an HTTP test is not executed in a single process it doesn’t require as many Load Injector resources as the Postman Collection Task. Usually, for the HTTP test you can run from 500 to 1000 concurrent users on a single Load Injector Server. So you can scale the payload into much higher numbers than with Postman Collection Task without a significant increase in overall cost.
Creating a Task
Before you begin the task configuration, prepare the Postman Collection to be imported to Dotcom-Monitor as described in Uploading Postman Collection to Dotcom-Monitor.
Once you have selected the Postman Collection task, you will be prompted to import a Postman collection and adjust the task settings.
Click Import and select a suitable option to upload the collection. You can upload the JSON file with the Postman collection or provide the public link to the collection (if it was published). The collection script will be displayed in the Collection Requests section.
An interval delay (in seconds) between each request in the collection. By default, we use the Delay time that was set in Postman Collection Runner. The Delay time is considered in the response time calculation.
A time interval in seconds the task should wait for the completion of requests and collection execution before ending the task and returning an error.
A time interval in seconds the task should wait for a response on a single request from the collection.
A time interval in seconds the task should wait for the assertion script completion before ending the task and returning an error. The maximum script timeout is 30 seconds.