Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spurtest.com/llms.txt

Use this file to discover all available pages before exploring further.

​
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

​
What Happens in Manual Runs

Snoozing behaves differently depending on how you trigger the run:
Run typeSnoozed test behaviour
Run the full suiteSnoozed test is skipped
Run the specific test individuallyTest runs as normal
Test plan runSnoozed test is skipped
CI/CD triggered runSnoozed test is skipped
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.