Monitor scheduling in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Monitor Scheduling in Postman?

Monitor Scheduling in Postman allows you to run your API tests automatically at set times or intervals without manual intervention.

beginner

How do you set the frequency of a Postman Monitor?

You set the frequency by choosing options like every 5 minutes, hourly, daily, or weekly when configuring the monitor's schedule.

beginner

Why is Monitor Scheduling useful in API testing?

It helps catch issues early by running tests regularly, like checking if an API is up or if responses are correct, without needing to run tests manually.

intermediate

What happens if a scheduled Postman Monitor test fails?

Postman sends a notification email to the monitor owner with details about the failure so they can fix the problem quickly.

intermediate

Can you pause or disable a Postman Monitor schedule?

Yes, you can pause or disable a monitor anytime to stop it from running until you want it to start again.

What does Monitor Scheduling in Postman allow you to do?

A Run API tests automatically at set times

B Manually run tests only

C Create new APIs

D Edit API responses

Monitor Scheduling lets you run tests automatically on a schedule without manual effort.

Which of these is NOT a scheduling option in Postman Monitors?

A Hourly

B Yearly

C Every 10 minutes

D Every 5 minutes

Postman does not offer a yearly schedule option for monitors.

What kind of notification does Postman send if a monitor test fails?

A Email notification

B No notification

C Phone call

D SMS message

Postman sends an email notification to the monitor owner on test failure.

Can you stop a Postman Monitor from running temporarily?

A No, once started it runs forever

B Only by deleting it

C Only by changing the API

D Yes, by pausing or disabling it

You can pause or disable a monitor to stop it temporarily.

Why is scheduling monitors helpful in API testing?

A To avoid running tests

B To create new APIs

C To catch API issues early automatically

D To edit API documentation

Scheduled monitors run tests regularly to find problems early without manual effort.

Explain how you would set up a monitor schedule in Postman and why it is useful.

Think about how scheduling saves time and helps catch problems early.

Describe what happens when a scheduled Postman monitor test fails and how you can manage the monitor.

Consider the alert system and control options for monitors.

Practice

1. What is the main purpose of Monitor scheduling in Postman?

easy

A. To run API tests automatically at set times

B. To manually trigger API tests whenever needed

C. To write new API test scripts

D. To share API collections with team members

Solution

1. Step 1: Understand what monitor scheduling does

   Monitor scheduling runs API tests automatically without manual intervention.

2. Step 2: Compare options with this purpose

   Only To run API tests automatically at set times describes automatic running at set times, matching monitor scheduling.

3. Final Answer:

   To run API tests automatically at set times -> Option A

4. Quick Check:

   Monitor scheduling = automatic test runs [OK]

Hint: Remember: scheduling means automatic timing [OK]

Common Mistakes:

• Confusing manual triggering with scheduling
• Thinking scheduling creates tests
• Mixing sharing collections with scheduling

2. Which of the following is the correct way to set a monitor schedule in Postman?

easy

A. Schedule monitors only via Postman desktop app settings

B. Write a script in the Tests tab to schedule the monitor

C. Use the Runner tab to schedule monitor runs

D. Go to Monitors tab, select collection, then set frequency and time

Solution

1. Step 1: Identify where scheduling is set in Postman

   Scheduling is done in the Monitors tab by selecting a collection and setting frequency/time.

2. Step 2: Check other options for correctness

   The other options are incorrect because scheduling is not done via desktop app settings, scripts, or the Runner tab.

3. Final Answer:

   Go to Monitors tab, select collection, then set frequency and time -> Option D

4. Quick Check:

   Monitors tab = schedule location [OK]

Hint: Set schedules only in Monitors tab [OK]

Common Mistakes:

• Trying to schedule in Runner tab
• Writing scripts to schedule
• Looking for schedule in desktop app settings

3. Consider this monitor schedule set to run every day at 9:00 AM UTC. If today is Monday 8:00 AM UTC and you create the monitor now, when will the first run happen?

medium

A. Immediately after creation

B. Tuesday at 9:00 AM UTC (next day)

C. Monday at 9:00 AM UTC (in 1 hour)

D. Monday at 8:00 AM UTC (now)

Solution

1. Step 1: Understand the schedule timing

   The monitor runs daily at 9:00 AM UTC. Current time is Monday 8:00 AM UTC.

2. Step 2: Calculate next run time

   Since 9:00 AM is 1 hour ahead, the first run will be Monday at 9:00 AM UTC.

3. Final Answer:

   Monday at 9:00 AM UTC (in 1 hour) -> Option C

4. Quick Check:

   Next run = next scheduled time after now [OK]

Hint: Next run is next scheduled time after current time [OK]

Common Mistakes:

• Assuming immediate run on creation
• Choosing next day instead of same day if time not passed
• Confusing current time with scheduled time

4. You set a monitor to run every 2 hours but notice it only runs once a day. What is the most likely cause?

medium

A. The schedule frequency was set incorrectly to daily instead of every 2 hours

B. The API collection has no tests, so monitor skips runs

C. Postman monitors cannot run more than once a day

D. You need to restart Postman app to apply schedule changes

Solution

1. Step 1: Analyze the monitor schedule setting

   If monitor runs only once a day despite setting every 2 hours, likely the frequency was set wrong.

2. Step 2: Evaluate other options

   API collection without tests still runs; Postman supports multiple runs per day; restarting app not needed.

3. Final Answer:

   The schedule frequency was set incorrectly to daily instead of every 2 hours -> Option A

4. Quick Check:

   Check schedule frequency matches intended run rate [OK]

Hint: Verify schedule frequency matches your expectation [OK]

Common Mistakes:

• Assuming no tests stops runs
• Thinking Postman limits runs per day
• Restarting app fixes schedule issues

5. You want to monitor an API that updates every weekday at 6 PM UTC. Which schedule setup in Postman Monitor will best fit this requirement?

hard

A. Set monitor to run every hour and add a test to skip weekends

B. Set monitor to run daily at 6 PM UTC and disable weekends

C. Set monitor to run weekly on Friday at 6 PM UTC

D. Set monitor to run daily at 6 PM UTC without any weekend restrictions

Solution

1. Step 1: Identify the required schedule

   The API updates every weekday at 6 PM UTC, so monitor should run only Monday to Friday at that time.

2. Step 2: Match options to requirement

   Set monitor to run daily at 6 PM UTC and disable weekends sets daily at 6 PM and disables weekends, matching exactly. Set monitor to run every hour and add a test to skip weekends runs too often and relies on tests to skip. Set monitor to run weekly on Friday at 6 PM UTC runs only once a week. Set monitor to run daily at 6 PM UTC without any weekend restrictions runs on weekends too.

3. Final Answer:

   Set monitor to run daily at 6 PM UTC and disable weekends -> Option B

4. Quick Check:

   Schedule matches update days and time [OK]

Hint: Disable weekends to run only on weekdays [OK]

Common Mistakes:

• Running monitor on weekends unnecessarily
• Using tests to skip runs instead of schedule
• Setting weekly instead of daily schedule