Mock server limitations in Postman - Build an Automation Script

Verify mock server returns correct response and handles unsupported methods

Preconditions (3)

Step 1: Send a GET request to the mock server endpoint /user

Step 2: Verify the response status code is 200

Step 3: Verify the response body contains the expected JSON data

Step 4: Send a POST request to the mock server endpoint /user

Step 5: Verify the response status code is 404 or appropriate error indicating unsupported method

✅ Expected Result: The mock server returns the correct JSON response for GET /user with status 200, and returns an error status for unsupported POST /user request

Automation Requirements - Postman test scripts

Assertions Needed:

Response status code is 200 for GET /user

Response body matches expected JSON for GET /user

Response status code is 404 or error for POST /user

Best Practices:

Use pm.test and pm.response assertions

Use environment variables for mock server URL

Separate tests for different HTTP methods

Check both status code and response body

Automated Solution

Postman

const mockServerUrl = pm.environment.get('mockServerUrl');

// Test GET /user
pm.test('GET /user returns 200 and expected JSON', async () => {
    const getResponse = await pm.sendRequest({
        url: `${mockServerUrl}/user`,
        method: 'GET'
    });
    pm.expect(getResponse).to.have.property('code', 200);
    pm.expect(getResponse.json()).to.deep.equal({"id": 1, "name": "John Doe"});
});

// Test POST /user unsupported method
pm.test('POST /user returns error status for unsupported method', async () => {
    const postResponse = await pm.sendRequest({
        url: `${mockServerUrl}/user`,
        method: 'POST',
        body: {
            mode: 'raw',
            raw: JSON.stringify({"id": 2, "name": "Jane"})
        }
    });
    pm.expect(postResponse.code).to.be.oneOf([404, 405]);
});

This Postman test script uses pm.sendRequest to send HTTP requests to the mock server URL stored in an environment variable.

First, it sends a GET request to /user and asserts the response status code is 200 and the JSON body matches the expected user data.

Second, it sends a POST request to the same endpoint, which is unsupported by the mock server, and asserts the response status code is either 404 or 405, indicating the method is not allowed.

Using pm.test groups assertions clearly, and pm.expect checks the response properties. This approach verifies mock server limitations on supported HTTP methods.

Common Mistakes - 3 Pitfalls

Hardcoding the mock server URL inside the test script

Not checking the response status code for unsupported methods

Using synchronous pm.sendRequest calls without waiting for response

Bonus Challenge

Now add data-driven testing with 3 different user IDs for GET /user endpoint

Show Hint

Practice

1. Which of the following is a limitation of Postman mock servers?

easy

A. They cannot execute real backend logic or database queries.

B. They can modify data in a real database.

C. They automatically update responses based on user input.

D. They provide unlimited concurrent connections without delay.

Solution

1. Step 1: Understand what mock servers do

   Mock servers simulate API responses without running real backend code or accessing databases.

2. Step 2: Identify the limitation

   Since mock servers only return fixed responses, they cannot execute real logic or database queries.

3. Final Answer:

   They cannot execute real backend logic or database queries. -> Option A

4. Quick Check:

   Mock servers = fixed responses only [OK]

Hint: Mock servers return fixed data, no real logic [OK]

Common Mistakes:

• Thinking mock servers can update real databases
• Assuming mock servers adapt responses dynamically
• Believing mock servers handle unlimited traffic without limits

2. Which syntax correctly defines a mock server response in Postman?

easy

A. { "statusCode": 200, "content": "Success" }

B. { status: 200, body: { message: 'Success' } }

C. { "status": 200, "body": "{\"message\": \"Success\"}" }

D. { "code": 200, "response": "Success" }

Solution

1. Step 1: Review Postman mock response format

   Postman mock responses use JSON with keys like "status" and a stringified JSON body.

2. Step 2: Check each option

   { "status": 200, "body": "{\"message\": \"Success\"}" } uses correct keys and stringifies the body JSON properly. Others use incorrect keys or formats.

3. Final Answer:

   { "status": 200, "body": "{\"message\": \"Success\"}" } -> Option C

4. Quick Check:

   Correct keys and stringified body = { "status": 200, "body": "{\"message\": \"Success\"}" } [OK]

Hint: Use "status" and stringified JSON body keys [OK]

Common Mistakes:

• Using unquoted keys in JSON
• Not stringifying the body JSON
• Using wrong key names like 'code' or 'statusCode'

3. Given this Postman mock server setup:

{ "status": 404, "body": "{\"error\": \"Not Found\"}" }

What will be the HTTP status code and response body when the mock server is called?

medium

A. Status 500 with body {"error": "Not Found"}

B. Status 200 with body {"error": "Not Found"}

C. Status 404 with empty body

D. Status 404 with body {"error": "Not Found"}

Solution

1. Step 1: Read the mock response definition

   The mock response sets status to 404 and body to a JSON string with error message.

2. Step 2: Determine the actual response

   When called, the mock server returns status 404 and the body parsed as JSON {"error": "Not Found"}.

3. Final Answer:

   Status 404 with body {"error": "Not Found"} -> Option D

4. Quick Check:

   Status and body match mock setup = Status 404 with body {"error": "Not Found"} [OK]

Hint: Status code matches mock's "status" field [OK]

Common Mistakes:

• Assuming default 200 status code
• Ignoring the body content
• Confusing status 404 with 500

4. You created a Postman mock server but your app always receives the same response regardless of request parameters. What is the most likely cause?

medium

A. Mock servers return fixed responses and do not process request parameters.

B. Your request URL is incorrect and does not reach the mock server.

C. The mock server is down and returning cached responses.

D. You forgot to enable dynamic response scripting in the mock server.

Solution

1. Step 1: Understand mock server behavior

   Postman mock servers return fixed responses based on saved examples; they do not run logic or read parameters.

2. Step 2: Analyze the symptom

   Receiving the same response regardless of parameters matches fixed response behavior, not a connectivity or config issue.

3. Final Answer:

   Mock servers return fixed responses and do not process request parameters. -> Option A

4. Quick Check:

   Fixed response = no parameter processing [OK]

Hint: Mock servers ignore request parameters, always fixed response [OK]

Common Mistakes:

• Assuming mock servers run backend logic
• Blaming network or server downtime incorrectly
• Expecting dynamic responses without scripting support

5. You want to test different API error scenarios using a Postman mock server. Which limitation should you consider when designing your tests?

hard

A. Mock servers can connect to real databases to fetch error details dynamically.

B. Mock servers cannot simulate dynamic errors based on request content; you must create separate examples for each error.

C. Mock servers automatically generate error responses based on request headers.

D. Mock servers can run custom scripts to change responses during runtime.

Solution

1. Step 1: Recall mock server capabilities

   Postman mock servers return fixed responses from saved examples and do not run dynamic logic or scripts.

2. Step 2: Understand error simulation approach

   To test different errors, you must create multiple saved examples with fixed error responses; dynamic error generation is not possible.

3. Final Answer:

   Mock servers cannot simulate dynamic errors based on request content; you must create separate examples for each error. -> Option B

4. Quick Check:

   Fixed examples needed for each error scenario [OK]

Hint: Create separate examples for each error scenario [OK]

Common Mistakes:

• Expecting dynamic error generation from mock servers
• Assuming mock servers connect to real databases
• Thinking mock servers run runtime scripts