Monitor scheduling in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Monitor Scheduling Frequency

In Postman Monitor scheduling, what does setting the frequency to every 12 hours mean?

A The monitor runs once a day at 12 PM.

B The monitor runs every 12 minutes.

C The monitor runs twice a day, once every 12 hours.

D The monitor runs every 24 hours twice.

💡 Hint

Think about how many times 12 hours fits into a day.

Setting the frequency to every 12 hours means the monitor runs two times per day, spaced 12 hours apart.

❓ Predict Output

intermediate

Output of Monitor Schedule Setup Code

What will be the result of this Postman Monitor scheduling setup code snippet?

Postman

pm.monitor.schedule({
  interval: 'PT1H',
  timezone: 'UTC'
});
pm.test('Schedule interval test', () => {
  pm.expect(pm.monitor.schedule().interval).to.eql('PT1H');
});

A Test passes because interval is set to 1 hour.

B Test fails because interval is missing.

C Syntax error due to wrong method usage.

D Test fails because timezone is not validated.

💡 Hint

Check if the interval is correctly set and retrieved.

The code sets the monitor schedule interval to 1 hour (PT1H) and the test confirms this value, so the test passes.

❓ assertion

advanced

Correct Assertion for Monitor Next Run Time

Which assertion correctly verifies that the next scheduled run time of a Postman Monitor is in the future?

A pm.expect(new Date(pm.monitor.nextRun)).to.be.below(new Date());

B pm.expect(new Date(pm.monitor.nextRun)).to.be.above(new Date());

C pm.expect(pm.monitor.nextRun).to.eql(new Date());

D pm.expect(pm.monitor.nextRun).to.be.null;

💡 Hint

Think about comparing dates to check if nextRun is after now.

The assertion checks that the nextRun date is greater (in the future) than the current date, which is correct.

🔧 Debug

advanced

Identify the Bug in Monitor Scheduling Script

What is the bug in this Postman Monitor scheduling script?

Postman

pm.monitor.schedule({
  interval: 'PT24H',
  timezone: 'UTC'
});

if(pm.monitor.schedule().interval === 'PT12H') {
  console.log('Monitor runs every 12 hours');
}

A pm.monitor.schedule() cannot be called twice.

B The interval value 'PT24H' is invalid format.

C The timezone 'UTC' is not supported.

D The if condition uses assignment (=) instead of comparison (== or ===).

💡 Hint

Look carefully at the if statement condition.

The if condition mistakenly uses assignment (=) instead of comparison (== or ===), causing a logic error.

❓ framework

expert

Best Practice for Scheduling Monitors in Postman CI/CD Pipeline

In a CI/CD pipeline using Postman Monitors, which scheduling approach ensures tests run only after successful code deployment?

A Trigger the monitor run manually after deployment completes.

B Set the monitor to run daily at midnight.

C Use a fixed schedule and ignore deployment events.

D Schedule the monitor to run every hour regardless of deployment status.

💡 Hint

Consider how to align monitor runs with deployment success.

Triggering the monitor manually after deployment ensures tests run only when new code is deployed, avoiding false failures.

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