Alert configuration in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an alert in Postman?

An alert in Postman is a notification that informs you about important events or issues during API testing, such as failures or threshold breaches.

beginner

How do you configure an alert in Postman?

You configure an alert by setting conditions on your tests or monitors, such as response time limits or test failures, and specifying how you want to be notified.

intermediate

What types of notifications can Postman alerts send?

Postman alerts can send notifications via email, Slack, or webhook integrations to inform you immediately when an alert condition is met.

beginner

Why is alert configuration important in API testing?

Alert configuration helps you quickly detect and respond to API issues, ensuring your APIs work reliably and reducing downtime.

beginner

What is a common condition used in Postman alert configuration?

A common condition is checking if a test fails or if the response time exceeds a set threshold, triggering an alert.

What triggers an alert in Postman?

A API documentation update

B Successful API response

C Manual user action

D A test failure or threshold breach

Alerts are triggered when tests fail or when response times exceed set limits.

Which notification method is NOT supported by Postman alerts?

A SMS

B Slack

C Email

D Webhook

Postman supports email, Slack, and webhook notifications but does not natively support SMS.

Why should you configure alerts in your API tests?

A To ignore test failures

B To get notified about issues quickly

C To slow down test execution

D To increase API response time

Alerts help you get notified quickly about problems so you can fix them.

Which condition can be used to trigger an alert in Postman?

A Response time less than 100ms

B Test passes successfully

C Response time exceeds threshold

D API returns status 200

Alerts are triggered when response time exceeds a set threshold, not when it is below.

Where do you configure alerts in Postman?

A In the monitor or test settings

B In the collection runner

C In the environment variables

D In the API documentation

Alerts are configured in monitor or test settings where you define conditions and notifications.

Explain how to set up an alert in Postman and why it is useful.

Think about what you want to watch for and how you want to be told.

Describe common alert conditions and notification options available in Postman.

Focus on what triggers alerts and how you get notified.

Practice

1. What is the main purpose of configuring alerts in Postman during API testing?

easy

A. To notify testers when a test condition fails

B. To automatically fix API errors

C. To generate API documentation

D. To speed up API response times

Solution

1. Step 1: Understand alert purpose in testing

   Alerts are used to inform testers about issues or failures during tests.

2. Step 2: Identify correct alert function

   Alerts notify when test conditions fail, helping catch problems early.

3. Final Answer:

   To notify testers when a test condition fails -> Option A

4. Quick Check:

   Alerts = Notifications on failure [OK]

Hint: Alerts notify failures, not fix or document [OK]

Common Mistakes:

• Thinking alerts fix errors automatically
• Confusing alerts with documentation tools
• Assuming alerts improve response speed

2. Which of the following is the correct way to set an alert message in a Postman test script when a response status is not 200?

easy

A. pm.test('Status is 200', () => pm.response.to.have.status(200));

B. pm.alert('Status is not 200');

C. pm.test('Status is 200', () => { if(pm.response.code !== 200) pm.alert('Status is not 200'); });

D. pm.response.alert('Status check');

Solution

1. Step 1: Identify correct test syntax

   Postman uses pm.test() to define tests and pm.response.to.have.status() to check status.

2. Step 2: Check alert usage

   pm.alert() is not a valid Postman function; alerts come from test failures.

3. Final Answer:

   pm.test('Status is 200', () => pm.response.to.have.status(200)); -> Option A

4. Quick Check:

   Use pm.test with assertions [OK]

Hint: Use pm.test with assertions, no pm.alert function [OK]

Common Mistakes:

• Using pm.alert which does not exist
• Trying to call alert on response object
• Not using pm.test for assertions

3. Given this Postman test script:

pm.test('Response time is less than 500ms', () => {
  pm.expect(pm.response.responseTime).to.be.below(500);
});

What will happen if the response time is 600ms?

medium

A. The test will pass and no alert is shown

B. The test will pass but an alert is triggered

C. The script will cause a syntax error

D. The test will fail and an alert is triggered

Solution

1. Step 1: Understand the test condition

   The test expects response time below 500ms.

2. Step 2: Analyze response time 600ms

   600ms is above 500ms, so the condition fails and test fails.

3. Final Answer:

   The test will fail and an alert is triggered -> Option D

4. Quick Check:

   Fail if responseTime >= 500ms [OK]

Hint: Fail test if condition false triggers alert [OK]

Common Mistakes:

• Assuming test passes despite failure
• Thinking alerts show on pass
• Confusing syntax error with test failure

4. You wrote this Postman test script:

pm.test('Check status', () => {
  pm.expect(pm.response.status).to.equal(200);
});

But the test always fails even when the API returns 200. What is the error?

medium

A. pm.expect is used incorrectly

B. pm.test syntax is wrong

C. pm.response.status should be pm.response.code

D. The API never returns 200

Solution

1. Step 1: Check property for status code

   Postman uses pm.response.code for status code, not pm.response.status.

2. Step 2: Correct the property usage

   Replace pm.response.status with pm.response.code to fix the test.

3. Final Answer:

   pm.response.status should be pm.response.code -> Option C

4. Quick Check:

   Use pm.response.code for status [OK]

Hint: Use pm.response.code, not pm.response.status [OK]

Common Mistakes:

• Using pm.response.status instead of pm.response.code
• Misusing pm.expect syntax
• Assuming API never returns 200 without checking

5. You want to configure an alert in Postman that triggers only when the response JSON has a field error set to true. Which test script correctly sets this alert?

hard

A. pm.test('Error field check', () => {
pm.expect(pm.response.json().error).to.be.false;
});

B. pm.test('Error field check', () => {
const json = pm.response.json();
pm.expect(json.error).to.eql(true);
});

C. pm.test('Error field check', () => {
const json = pm.response.json();
if(json.error === true) pm.alert('Error found');
});

D. pm.test('Error field check', () => {
pm.response.to.have.jsonBody('error', true);
});

Solution

1. Step 1: Understand how to check JSON field in Postman

   Use pm.response.json() to parse JSON, then assert field value.

2. Step 2: Identify correct assertion syntax

   pm.expect(...).to.eql(true) correctly asserts that error is true, triggering failure if not.

3. Step 3: Evaluate options

   pm.test('Error field check', () => { pm.expect(pm.response.json().error).to.be.false; }); expects error to be false, which is opposite of requirement; pm.test('Error field check', () => { const json = pm.response.json(); if(json.error === true) pm.alert('Error found'); }); uses invalid pm.alert; pm.test('Error field check', () => { pm.response.to.have.jsonBody('error', true); }); uses invalid method.

4. Final Answer:

   pm.test('Error field check', () => { const json = pm.response.json(); pm.expect(json.error).to.eql(true); }); -> Option B

5. Quick Check:

   Use pm.expect(...).to.eql(true) to assert error true [OK]

Hint: Use pm.expect with .to.eql(true) for boolean alerts [OK]

Common Mistakes:

• Using pm.alert which does not exist
• Incorrect assertion methods
• Not parsing JSON before checking