A failure without a record is just a rumor.

Full bug lifecycle tracking. Quality-gated releases. Baseline snapshots for regression comparison. Every failure accounted for, every release earned.

Bug Lifecycle

NEW → TRIAGED → IN_PROGRESS → FIXED → VERIFIED → REOPENED → CLOSED → WONT_FIX.

Severity (CRITICAL, MAJOR, MINOR, TRIVIAL), priority, assignee, reporter, environment, found-in version, and fix version. Link to the triage decision that created it.

Stats by status and severity. Not a bug tracker tacked onto a QA tool — a first-class defect management workflow.

Bug Lifecycle
NEW
TRIAGED
IN_PROGRESS
FIXED
VERIFIED
CLOSED

Quality Gates

Every release can carry three gates: minimum pass rate, maximum critical bug count, maximum blocker bug count. Set them. RuyQA enforces them.

A release in CANDIDATE status stays there until the data says it's ready. Statuses: PLANNED, IN_PROGRESS, CANDIDATE, SHIPPED, ROLLED_BACK.

If a human overrides a gate, it's logged. The release still ships. The decision is still auditable.

Quality Gates — Release v2.5
Min pass rate
≥ 95%
PASS
Max critical bugs
≤ 2
PASS
Max blocker bugs
0
FAIL
Status: CANDIDATE — gates not cleared

Baselines

Snapshot the state of your test results at any point in time. Compare two baselines: new failures, tests that were fixed, tests that regressed.

Source every baseline to its originating run — automation or manual. Know exactly what state you're comparing against.

Baseline Comparison
Baseline: v2.4Current: v2.5
New failures3
Fixed tests12
Regressions2

Ship with confidence.

Every bug tracked, every release gated, every baseline compared.

Start Free Trial