Load testing basics (Postman) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the number of iterations for a Postman load test.

Postman

pm.environment.set('iterations', [1]);

Drag options to blanks, or click blank then click option'

A100

B'ten'

Ctrue

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a number for iterations.

The number of iterations must be a numeric value like 100 to run the load test multiple times.

2fill in blank

medium

Complete the code to check if the response status code is 200 in a Postman test script.

Postman

pm.test('Status code is 200', function () { pm.response.to.have.status([1]); });

Drag options to blanks, or click blank then click option'

A404

B'200'

C200

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string '200' instead of number 200.

The status code 200 means the request was successful. It should be a number, not a string.

3fill in blank

hard

Fix the error in the Postman test script to correctly check if response time is less than 500ms.

Postman

pm.test('Response time is less than 500ms', function () { pm.expect(pm.response.responseTime [1] 500).to.be.true(); });

Drag options to blanks, or click blank then click option'

A>

B<

C==

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' or '>' instead of '<'.

The operator '<' checks if the response time is less than 500 milliseconds.

4fill in blank

hard

Fill both blanks to create a Postman test that checks if the response body contains the word 'success' and the status code is 200.

Postman

pm.test('Body contains success and status is 200', function () { pm.expect(pm.response.text()).[1]('success'); pm.response.to.have.status([2]); });

Drag options to blanks, or click blank then click option'

Aincludes

B404

C200

DindexOf

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'indexOf' without comparison, or wrong status code.

'includes' checks if the response text contains 'success'. The status code 200 means OK.

5fill in blank

hard

Fill all three blanks to create a Postman test that checks if the JSON response has a 'status' key equal to 'ok', and the response time is less than 300ms.

Postman

pm.test('Status is ok and response time is fast', function () { const jsonData = pm.response.json(); pm.expect(jsonData.[1]).to.eql([2]); pm.expect(pm.response.responseTime [3] 300).to.be.true(); });

Drag options to blanks, or click blank then click option'

Astatus

B'ok'

C<

DresponseTime

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong key name, missing quotes around 'ok', or wrong operator for time.

We check the 'status' key in JSON equals 'ok' (string), and response time is less than 300ms.

Practice

1. What is the main purpose of load testing in Postman?

easy

A. To check how many users the app can handle at the same time

B. To find syntax errors in API requests

C. To test the UI responsiveness of the app

D. To verify database schema correctness

Solution

1. Step 1: Understand load testing goal

   Load testing is about simulating many users to see how the app performs under stress.

2. Step 2: Match with Postman usage

   Postman can send multiple requests to simulate users, so it helps check app capacity.

3. Final Answer:

   To check how many users the app can handle at the same time -> Option A

4. Quick Check:

   Load testing = user capacity check [OK]

Hint: Load testing = many users at once [OK]

Common Mistakes:

• Confusing load testing with syntax checking
• Thinking load testing checks UI only
• Mixing load testing with database tests

2. Which Postman feature allows you to run multiple requests repeatedly for load testing?

easy

A. Postman Runner

B. Postman Console

C. Postman Monitor

D. Postman Collection Editor

Solution

1. Step 1: Identify Postman features for running requests

   Postman Runner lets you run a collection of requests multiple times.

2. Step 2: Match feature to load testing

   Running requests repeatedly simulates load, so Runner is the correct tool.

3. Final Answer:

   Postman Runner -> Option A

4. Quick Check:

   Repeated runs = Postman Runner [OK]

Hint: Use Runner to repeat requests [OK]

Common Mistakes:

• Choosing Console which is for debugging
• Confusing Monitor with scheduled tests
• Thinking Collection Editor runs requests

3. Consider this Postman Runner setup: you run 100 iterations with 10 requests each. How many total requests are sent?

medium

A. 100

B. 10

C. 1000

D. 110

Solution

1. Step 1: Understand iterations and requests per iteration

   Each iteration runs 10 requests, and there are 100 iterations total.

2. Step 2: Calculate total requests

   Total requests = 100 iterations * 10 requests = 1000 requests.

3. Final Answer:

   1000 -> Option C

4. Quick Check:

   100 x 10 = 1000 [OK]

Hint: Multiply iterations by requests per iteration [OK]

Common Mistakes:

• Adding instead of multiplying
• Confusing iterations with requests
• Ignoring requests per iteration

4. You tried to run a load test in Postman Runner but only one request was sent repeatedly instead of the whole collection. What is the likely mistake?

medium

A. You forgot to save the collection

B. You selected a single request instead of the full collection

C. You used Monitor instead of Runner

D. You set iterations to 1

Solution

1. Step 1: Analyze the problem

   Only one request runs repeatedly, not the whole collection.

2. Step 2: Identify cause

   This happens if you run a single request in Runner instead of the entire collection.

3. Final Answer:

   You selected a single request instead of the full collection -> Option B

4. Quick Check:

   Single request run = wrong selection [OK]

Hint: Always select full collection for load test [OK]

Common Mistakes:

• Thinking iterations = 1 causes this
• Confusing Monitor with Runner
• Assuming saving fixes request selection

5. You want to perform a heavy load test beyond Postman's Runner limits. Which approach is best?

hard

A. Increase iterations in Postman Runner to 10,000

B. Use Postman Console to debug requests

C. Run Postman Monitor continuously for 24 hours

D. Use Newman in combination with a load testing tool like Apache JMeter

Solution

1. Step 1: Understand Postman Runner limits

   Postman Runner is good for basic load but not for very heavy or distributed load testing.

2. Step 2: Identify best heavy load testing method

   Newman can run collections from command line and can be integrated with tools like JMeter for heavy load.

3. Final Answer:

   Use Newman in combination with a load testing tool like Apache JMeter -> Option D

4. Quick Check:

   Heavy load = Newman + load tool [OK]

Hint: Combine Newman with load tools for heavy tests [OK]

Common Mistakes:

• Trying to increase Runner iterations too high
• Using Monitor for load testing
• Using Console for load testing