What is the main goal of load testing in Postman?
Think about what happens when many users use the system at the same time.
Load testing measures system behavior under expected user load to ensure stability and performance.
After running a load test with 50 virtual users for 1 minute in Postman, the average response time is 1200 ms, and error rate is 0%. What does this indicate?
Consider what a 0% error rate means and if 1200 ms is acceptable.
An average response time of 1200 ms with zero errors means the API is stable and handles the load well.
Which Postman test script assertion correctly checks that the response time is less than 2000 milliseconds during a load test?
pm.test('Response time is less than 2000ms', function () { // Fill in assertion here });
Look for the correct property name and assertion method to check less than a value.
The property pm.response.responseTime holds the response time in ms. The assertion to.be.below(2000) checks it is less than 2000 ms.
Given this Postman test script snippet for load testing, what error will occur?
pm.test('Status code is 200', () => { pm.expect(pm.response.status).to.eql(200); });
Check the correct property name for status code in Postman response object.
The correct property for status code is pm.response.code, not pm.response.status (which returns the status text like "OK"). Expecting the status text to equal 200 causes an AssertionError.
Which sequence correctly describes the steps to configure a load test with 100 virtual users running for 2 minutes in Postman Collection Runner?
Remember that delay is the wait time between requests, and iterations control how many times the collection runs.
First select the collection, then open Runner, set iterations (to control number of runs), then set delay (to control wait time between requests).