Using mock server URL in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the mock server URL in Postman.

Postman

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

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

Ahttps://mockserver.example.com

Blocalhost:3000

Chttp://api.example.com

Dftp://mockserver

Attempts:

3 left

💡 Hint

Common Mistakes

Using localhost or non-HTTPS URLs for the mock server.

Using the real API URL instead of the mock server URL.

The mock server URL must be a valid HTTPS URL provided by Postman mock server, like 'https://mockserver.example.com'.

2fill in blank

medium

Complete the code to send a GET request to the mock server URL stored in environment variable.

Postman

pm.sendRequest(pm.environment.get('[1]') + '/users', function (err, res) { pm.test('Status is 200', function () { pm.expect(res).to.have.property('statusCode', 200); }); });

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

AmockUrl

BserverUrl

CapiUrl

DbaseUrl

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable name that does not exist in environment variables.

Forgetting to add the endpoint path after the base URL.

The environment variable 'baseUrl' holds the mock server URL, so we get it with pm.environment.get('baseUrl').

3fill in blank

hard

Fix the error in the test script to correctly check the response status code from the mock server.

Postman

pm.test('Response status is 200', function () { pm.expect(res.[1]).to.eql(200); });

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

Acode

BstatusCode

Cstatus

Dstatus_code

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'res.status' or 'res.code' which are undefined in Postman response object.

Using snake_case instead of camelCase for property names.

In Postman test scripts, the response status code is accessed via 'res.statusCode'.

4fill in blank

hard

Fill both blanks to create a test that checks the response body has a 'message' property equal to 'Success'.

Postman

pm.test('Body has success message', function () { pm.expect(res.[1]).to.have.property('[2]', 'Success'); });

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

Ajson()

Btext()

Cmessage

Dbody

Attempts:

3 left

💡 Hint

Common Mistakes

Using res.body instead of res.json() to access JSON properties.

Checking for wrong property names or values.

Use res.json() to parse the response body as JSON, then check it has property 'message' with value 'Success'.

5fill in blank

hard

Fill all three blanks to write a test that verifies the response header 'Content-Type' includes 'application/json'.

Postman

pm.test('Content-Type is JSON', function () { pm.expect(res.[1].get('[2]')).to.include('[3]'); });

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

Aheaders

Bheader

CContent-Type

Dapplication/json

Attempts:

3 left

💡 Hint

Common Mistakes

Using res.headers.get instead of res.header.get.

Checking for wrong header names or exact match instead of includes.

Use res.header.get('Content-Type') to get the header value, then check it includes 'application/json'.

Practice

1. What is the main purpose of using a mock server URL in Postman?

easy

A. To speed up the internet connection

B. To store user data permanently

C. To test API requests without needing the real backend server

D. To create a live production environment

Solution

1. Step 1: Understand what a mock server does

   A mock server simulates API responses without calling the real backend.

2. Step 2: Identify the main use case

   This helps test APIs when the real server is unavailable or to speed up development.

3. Final Answer:

   To test API requests without needing the real backend server -> Option C

4. Quick Check:

   Mock server = test without real backend [OK]

Hint: Mock servers simulate APIs without real backend [OK]

Common Mistakes:

• Thinking mock servers speed up internet
• Confusing mock server with data storage
• Assuming mock server is for production

2. Which of the following is the correct way to use a mock server URL in Postman?

easy

A. Replace the real API base URL with the mock server URL including the unique ID

B. Add the mock server URL as a query parameter to the real URL

C. Use the mock server URL only in the request headers

D. Append the mock server URL after the response body

Solution

1. Step 1: Understand mock server URL usage

   You replace the real API base URL with the mock server URL that includes the unique mock ID.

2. Step 2: Check other options

   Adding as query parameter, headers, or after response body is incorrect usage.

3. Final Answer:

   Replace the real API base URL with the mock server URL including the unique ID -> Option A

4. Quick Check:

   Mock URL replaces base URL [OK]

Hint: Mock URL replaces real API base URL [OK]

Common Mistakes:

• Adding mock URL as query parameter
• Using mock URL only in headers
• Appending mock URL after response

3. Given the mock server URL https://mockserver.com/12345/api/users, what will happen if you send a GET request to this URL in Postman?

medium

A. You will get a mocked response defined in the mock server for the /api/users endpoint

B. The request will fail because mock servers do not support GET requests

C. You will get a real response from the live backend server

D. Postman will ignore the mock server URL and use the environment variable URL

Solution

1. Step 1: Understand mock server behavior

   Mock servers return predefined responses for requests sent to their URLs.

2. Step 2: Analyze the given URL and request

   Sending GET to the mock URL returns the mocked response for /api/users.

3. Final Answer:

   You will get a mocked response defined in the mock server for the /api/users endpoint -> Option A

4. Quick Check:

   GET to mock URL returns mock response [OK]

Hint: GET to mock URL returns predefined mock response [OK]

Common Mistakes:

• Thinking mock servers reject GET requests
• Expecting real backend response
• Assuming environment variables override mock URL

4. You set the mock server URL incorrectly by missing the unique ID part, like https://mockserver.com/api/users. What issue will you face?

medium

A. The request will succeed and return the correct mock response

B. Postman will fail to route the request to the mock server and return an error

C. Postman will automatically add the missing unique ID

D. The request will be sent to the real backend server instead

Solution

1. Step 1: Identify the importance of unique ID in mock URL

   The unique ID is required to route requests to the correct mock server instance.

2. Step 2: Consequence of missing unique ID

   Without it, Postman cannot find the mock server and returns an error.

3. Final Answer:

   Postman will fail to route the request to the mock server and return an error -> Option B

4. Quick Check:

   Missing mock ID causes routing error [OK]

Hint: Always include unique ID in mock URL [OK]

Common Mistakes:

• Assuming Postman auto-fixes missing ID
• Expecting fallback to real backend
• Thinking request will succeed without ID

5. You want to test an API endpoint /products using a Postman mock server. Your mock server URL is https://mockserver.com/abcde. Which is the correct full URL to use in your request to get the mocked /products response?

hard

A. https://mockserver.com/api/abcde/products

B. https://mockserver.com/products/abcde

C. https://mockserver.com/abcde/api/products

D. https://mockserver.com/abcde/products

Solution

1. Step 1: Understand mock server URL structure

   The mock server URL includes the unique ID, followed by the API endpoint path.

2. Step 2: Construct the correct full URL

   Append the endpoint /products directly after the unique ID in the URL.

3. Final Answer:

   https://mockserver.com/abcde/products -> Option D

4. Quick Check:

   Mock URL + endpoint path = full request URL [OK]

Hint: Append endpoint path after mock server URL with ID [OK]

Common Mistakes:

• Placing unique ID after endpoint path
• Adding extra /api/ segment incorrectly
• Mixing order of ID and endpoint