When to Use This Monitor
- Surface suppressed tests: Find tests that someone marked as skip (
.skip,xtest,xit) and never re-enabled. - Track intentional skips: Apply a
skippedlabel so dashboards reflect tests that are excluded from runs, giving a more accurate picture of suite coverage. - Scope to specific branches: Detect skips on main or release branches where a skipped test represents a gap in coverage rather than a development convenience.
How It Works
The monitor counts the number of skipped runs for each test case within a configurable time window (in minutes). When a test accumulates at leastminSkippedCount skipped runs in that window, the monitor activates and applies the configured labels.
Resolution occurs after resolutionDays days pass with no new skipped runs recorded for that test on any monitored branch.
Configuration
Window
The time window controls how far back the monitor looks when counting skipped runs. A shorter window (e.g., 60 minutes) catches tests skipped in a burst around a specific CI run. A longer window (e.g., 2 days, 2880 minutes) catches tests that are habitually skipped across many runs.Min Skipped Count
Set this to 1 to flag any test the moment it skips a single run in the window. Set it higher to require repeated skips, filtering out tests that are skipped once for a legitimate reason (such as a flaky environment that resolves itself).Resolution Days
After a test stops being skipped, the monitor waitsresolutionDays before resolving. This prevents the label from flickering on and off for tests that skip intermittently.
Branch Scope
Use branch patterns to limit detection to branches where a skipped test is significant. For example, monitoring onlymain means tests skipped on feature branches do not trigger the monitor.