Skip to main content

​
Overview

Snoozing a test temporarily pauses it from running. This page explains what happens to your runs when a test is snoozed. For how to snooze or unsnooze a test, see Snooze Tests.

​
What Happens to Scheduled Runs

When a test is snoozed, it is automatically skipped across all automated run contexts for the duration of the snooze period:
  • Scheduled test plans — the snoozed test is excluded from every scheduled execution
  • CI/CD pipeline runs — the test is skipped when your pipeline triggers a test plan
  • Suite runs — the test does not execute when the full suite is run
Any tests that depend on the snoozed test are also paused. Spur skips the entire dependency chain below a snoozed test to prevent failures caused by missing setup steps.
Snoozing a test pauses it and all of its dependent child tests across all automated run contexts until the snooze expires or is manually removed.
Screenshot2026 02 19at7 37 31PM

Flow view showing a snoozed test and its paused dependent tests

​
What Happens in Manual Runs

Snoozing behaves differently depending on how you trigger the run: If you need to run a snoozed test to debug or verify a fix, trigger it directly from the test rather than from the suite or test plan.
Running a snoozed test individually does not remove the snooze. It will continue to be skipped in all automated contexts until you manually unsnooze it or the period expires.