Condition block in Postman - Build an Automation Script

Validate response status and content using condition block in Postman test script

Preconditions (2)

Step 1: Send a GET request to https://jsonplaceholder.typicode.com/posts/1

Step 2: In the Tests tab, write a condition block to check if the response status code is 200

Step 3: If status code is 200, assert that the response body contains a userId field with value 1

Step 4: If status code is not 200, assert that the response body contains an error message

✅ Expected Result: Test passes if status code is 200 and userId is 1; otherwise, test fails with appropriate error assertion

Automation Requirements - Postman test scripts (JavaScript)

Assertions Needed:

Assert response status code equals 200

Assert response body contains userId with value 1 when status is 200

Assert response body contains error message when status is not 200

Best Practices:

Use pm.response.to.have.status for status code assertion

Use pm.expect for assertions

Use if-else condition blocks to handle different response scenarios

Keep test scripts readable and maintainable

Automated Solution

Postman

pm.test('Condition block test for status and response body', function () {
    if (pm.response.code === 200) {
        pm.expect(pm.response.json()).to.have.property('userId', 1);
    } else {
        pm.expect(pm.response.text()).to.include('error');
    }
});

This test script uses a condition block to check the response status code.

If the status code is 200, it asserts that the JSON response has a property userId equal to 1.

If the status code is not 200, it asserts that the response text includes the word error.

This approach ensures the test adapts to different response scenarios and verifies the expected content accordingly.

Common Mistakes - 3 Pitfalls

Not checking the response status code before asserting response body

Using pm.response.json() without verifying response is JSON

Hardcoding assertions without condition blocks

Bonus Challenge

Now add data-driven testing with 3 different API endpoints and validate their status and response content using condition blocks

Show Hint

Practice

1. What is the main purpose of a condition block in Postman tests?

easy

A. To send multiple requests at once

B. To run code only when a specific condition is true

C. To store variables permanently

D. To format the response body

Solution

1. Step 1: Understand the role of condition blocks

   Condition blocks like if let you run code only when certain conditions are met.

2. Step 2: Compare with other options

   Sending requests, storing variables, or formatting responses are different features, not condition blocks.

3. Final Answer:

   To run code only when a specific condition is true -> Option B

4. Quick Check:

   Condition block = run code if true [OK]

Hint: Condition blocks run code only if conditions are true [OK]

Common Mistakes:

• Confusing condition blocks with request sending
• Thinking condition blocks store variables
• Assuming condition blocks format responses

2. Which of the following is the correct syntax for a condition block in Postman test scripts?

easy

A. check (pm.response.code === 200) { console.log('Success'); }

B. when (pm.response.code == 200) { console.log('Success'); }

C. if pm.response.code = 200 then { console.log('Success'); }

D. if (pm.response.code === 200) { console.log('Success'); }

Solution

1. Step 1: Identify correct JavaScript condition syntax

   Postman test scripts use JavaScript, so if (condition) { } is correct syntax.

2. Step 2: Check each option

   if (pm.response.code === 200) { console.log('Success'); } uses correct if with triple equals and braces. Others use invalid keywords or assignment instead of comparison.

3. Final Answer:

   if (pm.response.code === 200) { console.log('Success'); } -> Option D

4. Quick Check:

   Use if (condition) { } in Postman [OK]

Hint: Use JavaScript if (condition) { } syntax [OK]

Common Mistakes:

• Using wrong keywords like 'when' or 'check'
• Using single equals '=' instead of '==' or '==='
• Missing parentheses or braces

3. Given this Postman test script snippet:

if (pm.response.code === 404) {
    pm.test('Not Found', () => {
        pm.expect(pm.response.code).to.equal(404);
    });
} else {
    pm.test('Other status', () => {
        pm.expect(pm.response.code).to.not.equal(404);
    });
}

What test will run if the response code is 200?

medium

A. 'Not Found' test runs and passes

B. Both tests run and fail

C. 'Other status' test runs and passes

D. No tests run

Solution

1. Step 1: Analyze the condition with response code 200

   The if checks if code is 404; 200 is not 404, so else block runs.

2. Step 2: Identify which test runs in else block

   The else block runs a test named 'Other status' that expects code not to be 404, which is true for 200.

3. Final Answer:

   'Other status' test runs and passes -> Option C

4. Quick Check:

   Response 200 triggers else block test [OK]

Hint: If condition false, else block runs test [OK]

Common Mistakes:

• Assuming 'Not Found' test runs for 200
• Thinking both tests run simultaneously
• Believing no test runs if condition false

4. Identify the error in this Postman test script condition block:

if pm.response.code == 200 {
    pm.test('Status is 200', () => {
        pm.expect(pm.response.code).to.equal(200);
    });
}

medium

A. Missing parentheses around the condition

B. Using double equals instead of triple equals

C. Missing semicolon after pm.test

D. Incorrect function arrow syntax

Solution

1. Step 1: Check syntax of the if statement

   JavaScript requires parentheses around the condition in if, but here they are missing.

2. Step 2: Verify other syntax elements

   Double equals is allowed in JS, semicolon after pm.test is optional, and arrow function syntax is correct.

3. Final Answer:

   Missing parentheses around the condition -> Option A

4. Quick Check:

   Always use parentheses in if (condition) [OK]

Hint: Always wrap condition in parentheses in if statements [OK]

Common Mistakes:

• Omitting parentheses around condition
• Confusing == and === as syntax errors
• Expecting semicolons after function calls

5. You want to write a Postman test that checks if the response JSON has a status field equal to 'success'. If true, test should pass with message 'Success status'. Otherwise, it should fail with message 'Status not success'. Which condition block correctly implements this?

hard

A. if (pm.response.json().status === 'success') {
pm.test('Success status', () => {
pm.expect(true).to.be.true;
});
} else {
pm.test('Status not success', () => {
pm.expect.fail('Status not success');
});
}

B. if pm.response.json().status = 'success' {
pm.test('Success status', () => {
pm.expect(true).to.be.true;
});
} else {
pm.test('Status not success', () => {
pm.expect.fail('Status not success');
});
}

C. if (pm.response.json().status == 'success') {
pm.test('Success status', () => {
pm.expect(false).to.be.true;
});
} else {
pm.test('Status not success', () => {
pm.expect.fail('Status not success');
});
}

D. if (pm.response.json().status === 'success') {
pm.test('Success status', () => {
pm.expect.fail('Status not success');
});
} else {
pm.test('Status not success', () => {
pm.expect(true).to.be.true;
});
}

Solution

1. Step 1: Check condition syntax and comparison

   Correct syntax requires if (pm.response.json().status === 'success') with parentheses, strict equality ===, and proper JSON access. Other options lack parens, use assignment, wrong expectations, or swapped logic.

2. Step 2: Verify test pass/fail logic

   If true, pm.test('Success status', () => { pm.expect(true).to.be.true; }) passes. Else, pm.test('Status not success', () => { pm.expect.fail('Status not success'); }) fails with message.

3. Final Answer:

   if (pm.response.json().status === 'success') { pm.test('Success status', () => { pm.expect(true).to.be.true; }); } else { pm.test('Status not success', () => { pm.expect.fail('Status not success'); }); } -> Option A

4. Quick Check:

   Use strict equality and fail test in else block [OK]

Hint: Use if (condition) { pass } else { fail } pattern [OK]

Common Mistakes:

• Using single equals '=' instead of '==='
• Failing test inside success block
• Passing test inside failure block