Creating monitors in Postman - Quick Revision & Summary

Recall & Review

beginner

What is a monitor in Postman?

A monitor in Postman is a tool that runs your collections automatically at scheduled times to check if your APIs are working as expected.

beginner

How do you create a monitor in Postman?

You create a monitor by selecting a collection, setting a schedule, choosing an environment, and then saving it to run automatically.

beginner

Why is scheduling important when creating monitors?

Scheduling lets you run tests regularly without manual effort, helping catch issues early and ensuring API reliability.

intermediate

What can you do if a monitor run fails?

You can check the detailed run report to see which test failed, fix the issue in your API or tests, and rerun the monitor.

intermediate

What is the benefit of using environments with monitors?

Environments let you run the same tests with different settings like URLs or credentials, making monitors flexible for multiple setups.

What is the first step to create a monitor in Postman?

A Set the schedule

B Select a collection to monitor

C Choose an environment

D Write test scripts

You start by selecting the collection you want the monitor to run.

How often can you schedule a Postman monitor to run?

A Every 5 minutes or more

B Only manually

C Only weekly

D Only once a day

Postman monitors can be scheduled to run as frequently as every 5 minutes.

What does a monitor report show?

A API response times and test results

B Only the API response status

C Only the test script code

D User activity logs

Monitor reports include response times and whether tests passed or failed.

Why use environments with monitors?

A To write new test scripts

B To change the monitor schedule

C To run tests with different variables like URLs

D To share monitors with others

Environments allow running the same tests with different settings such as URLs or tokens.

What happens if a monitor test fails?

A Nothing happens

B The monitor stops running forever

C Postman deletes the collection

D You get a detailed report to investigate

You receive a detailed report to help find and fix the problem.

Explain the steps to create a monitor in Postman and why each step is important.

Think about what you need to run tests automatically and how to customize them.

Describe how using environments with monitors can help test APIs in different situations.

Consider how changing settings without changing tests saves time.

Practice

1. What is the main purpose of creating a monitor in Postman?

easy

A. To run API tests automatically on a schedule

B. To manually execute API requests one by one

C. To write new API test scripts

D. To create API documentation

Solution

1. Step 1: Understand what monitors do

   Monitors in Postman are designed to run tests automatically without manual intervention.

2. Step 2: Identify the main use

   They run API tests on a schedule to catch issues early.

3. Final Answer:

   To run API tests automatically on a schedule -> Option A

4. Quick Check:

   Monitors = Automated scheduled tests [OK]

Hint: Monitors run tests automatically, not manually [OK]

Common Mistakes:

• Thinking monitors are for manual testing
• Confusing monitors with writing test scripts
• Assuming monitors create documentation

2. Which of the following is required before creating a monitor in Postman?

easy

A. A manual test run report

B. An active Postman environment variable

C. A Postman workspace with no collections

D. A saved collection with tests

Solution

1. Step 1: Recall monitor prerequisites

   Monitors need a saved collection that contains tests to run automatically.

2. Step 2: Check other options

   Environment variables help but are not strictly required; a workspace without collections cannot run tests; manual reports are unrelated.

3. Final Answer:

   A saved collection with tests -> Option D

4. Quick Check:

   Monitor setup = saved collection needed [OK]

Hint: Monitors need collections with tests saved first [OK]

Common Mistakes:

• Assuming environment variables are mandatory
• Trying to create monitors without collections
• Confusing manual reports with monitor setup

3. Consider this scenario: You create a monitor for a collection that tests an API endpoint. The monitor is set to run every hour. What will happen if the API is down during a monitor run?

medium

A. The monitor will skip the test and report success

B. The monitor run will fail and report errors

C. The monitor will run tests but ignore failures

D. The monitor will automatically fix the API issue

Solution

1. Step 1: Understand monitor behavior on failure

   If the API is down, the requests in the collection will fail during the monitor run.

2. Step 2: Identify monitor reporting

   Monitors report test failures and errors; they do not skip or ignore failures, nor fix issues automatically.

3. Final Answer:

   The monitor run will fail and report errors -> Option B

4. Quick Check:

   API down = monitor reports failure [OK]

Hint: Monitors report errors if API is down during run [OK]

Common Mistakes:

• Thinking monitors skip failed tests
• Believing monitors fix API problems
• Assuming monitor reports success despite failures

4. You created a monitor but it never runs at the scheduled time. What is the most likely reason?

medium

A. The collection used by the monitor was deleted

B. The monitor schedule is set to run every minute

C. The monitor has no tests in the collection

D. The monitor is set to manual run only

Solution

1. Step 1: Check monitor prerequisites

   If the collection linked to the monitor is deleted, the monitor cannot run.

2. Step 2: Evaluate other options

   Running every minute is valid; having no tests means no failures but monitor still runs; monitors do not have manual-only mode.

3. Final Answer:

   The collection used by the monitor was deleted -> Option A

4. Quick Check:

   Deleted collection = monitor won't run [OK]

Hint: Deleted collection breaks monitor runs [OK]

Common Mistakes:

• Assuming schedule frequency stops runs
• Thinking monitors can be manual-only
• Confusing empty tests with no runs

5. You want to create a monitor that runs your API tests every day at 9 AM UTC and sends email alerts only if tests fail. Which steps should you follow?

hard

A. Create a new collection without tests, schedule monitor hourly, disable alerts

B. Save a collection with tests, create a monitor with no schedule, enable all alerts

C. Save a collection with tests, create a monitor scheduled daily at 9 AM UTC, enable email alerts on failure

D. Create a monitor without a collection, schedule daily, enable email alerts

Solution

1. Step 1: Prepare the collection

   You must have a saved collection that contains the API tests to run.

2. Step 2: Configure the monitor schedule and alerts

   Create a monitor scheduled daily at 9 AM UTC and enable email alerts only on test failures.

3. Final Answer:

   Save a collection with tests, create a monitor scheduled daily at 9 AM UTC, enable email alerts on failure -> Option C

4. Quick Check:

   Collection + daily schedule + alerts on failure = correct setup [OK]

Hint: Schedule monitor + enable alerts only on failure [OK]

Common Mistakes:

• Scheduling monitor without tests in collection
• Disabling alerts when failures occur
• Creating monitor without a collection