Skip to content

Test Suppression

Test suppression lets you acknowledge a known-failing test without blocking your CI pipeline. Suppressed tests are still tracked and reported, but they don't cause a non-zero exit code from the CLI.

How It Works

  1. A test fails in CI and is uploaded to Drape
  2. You suppress the test in the Drape UI, optionally linking a ticket
  3. On subsequent uploads, the CLI reports the test as "suppressed" rather than "failed"
  4. The exit code reflects only unsuppressed failures

SLAs

Suppressions have SLAs — a time limit by which the underlying issue should be fixed. When a suppression's SLA expires, Drape flags it so your team can prioritize the fix.

When to Use Suppression

  • Known infrastructure flakiness — a test fails due to an external dependency, not a code bug
  • Work-in-progress fixes — you've identified the issue and have a ticket, but the fix isn't ready yet
  • Environment-specific failures — a test that fails only in CI due to environment differences

Suppression is not a permanent solution — it's a way to unblock your team while tracking that the issue needs attention.