Skip to main content

Configure quality gates

Quality gates become useful when specs, tests, components, releases, and issues are consistently linked.

1. Assign components​

Create components for important product areas and assign specs and tests to them. Component grouping drives traceability and verdict breakdowns.

Link every test case to the spec it verifies:

tiden test link-spec <test-id> --spec-id <spec-id>

On a branch, review link proposals before merge.

3. Create releases​

Create releases from CI or the CLI:

tiden release create \
  --product-id <product-id> \
  --version "$RELEASE_VERSION" \
  --environment production

Use the same release value in telemetry SDKs.

4. Connect error tracking​

Production issues can block or affect gate results for release scopes when they are attributed to components.

5. Compute the gate​

Check main:

tiden gate check --product-id <product-id>

Check a release:

tiden gate check --product-id <product-id> --release <release-id>

6. Review traceability​

Open Traceability and fix:

  • Specs with no tests. Keep future work in Backlog: the gate does not count planned specs as missing tests. See Spec statuses.
  • Linked tests that have not run.
  • Components with concentrated failures.
  • Stale or missing release context.

7. Accept risk only deliberately​

Risk acceptance should explain why shipping is acceptable despite a soft signal. Use it for explicit business decisions, not for hiding missing tests.