How to create devices
If you have a collection of integration tests for internal API testing with Postman, but also need to set up tests from outside the local network, you can upload the Postman tests to Dotcom-Monitor. Using Dotcom-Monitor Postman Collection task you can create automated monitoring tests with alerting on errors occurred while monitoring, specify monitoring locations, a monitoring scheduler, filters, and set up reporting on monitoring results.
The collection of requests will be repeatedly executed with the specified frequency to perform the sequence of calls to the target Web API. Herewith, the assertions that were specified for the requests in Postman will be used to verify API responses. If any condition set by assertions is not met the task will be marked as failed.
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.
An HTTP request in the collection represents a separate task and will be charged according to your package.
See also approximate Pricing Matrix for WebView Monitoring (please see your account executive with questions).
Creating a Task
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.
By default, we import the collection settings from Postman. If it is necessary, you can change the values in the monitoring device settings.
An interval delay (in seconds) between each request in the collection. By default, we use the Delay time 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.
Script Timeout
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.