Monitor scheduling in Postman - Test Execution Trace

Test Overview

This test checks if a Postman monitor is scheduled correctly and runs at the expected time. It verifies that the monitor triggers and completes successfully.

Test Code - Postman Test Script

Postman

pm.test("Monitor runs successfully at scheduled time", function () {
    pm.expect(pm.response.code).to.equal(200);
    pm.expect(pm.response.json().status).to.equal("completed");
    pm.expect(pm.response.json().run_at).to.be.a('string');
});

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Postman environment ready with monitor scheduled	—	PASS
2	Monitor triggers at scheduled time	Monitor run initiated by Postman scheduler	—	PASS
3	Postman sends request and receives response	Response received with status code 200 and JSON body	pm.response.code == 200	PASS
4	Test script runs assertions on response	Response JSON contains status and run_at fields	pm.response.json().status == 'completed'	PASS
5	Test script checks run_at field is a string	run_at field present and is a string timestamp	pm.response.json().run_at is a string	PASS
6	Test completes successfully	Monitor run verified as successful and on schedule	—	PASS

Failure Scenario

Failing Condition: Monitor does not run at scheduled time or response status is not 'completed'

Execution Trace Quiz - 3 Questions

What does the test verify about the monitor's response status?

A It should be 'completed'

B It should be 'pending'

C It should be 'failed'

D It should be empty

Key Result

Always verify both the response status code and the expected data fields to confirm that scheduled monitors run correctly and complete as expected.

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