OMG QA helps QA teams, automated testing systems, and AI coding agents collaborate around quality findings, evidence, and fixes — from first failure to merged fix.
Built for teams that ship fast — developers, QA engineers, product owners, and AI agents working from one shared source of truth.
Bug, incident, risk, regression, feedback, observation, question — one unified inbox for your entire quality signal.
Screenshots, Playwright traces, HAR files and videos attached automatically at the moment of failure. No copy-paste.
Claude analyzes every finding on create: severity, duplicate detection, fix suggestion, and revenue-impact assessment.
14 governed tools via Model Context Protocol. Any compatible agent — Claude Code, Cursor, Codex — can create, search, and triage findings.
One config line. Every CI failure becomes a Finding in 4 seconds. Trace, video, screenshot attached and deduplicated automatically.
PRs, commits and CI runs linked to findings automatically. A finding moves to Ready for retest when its fixing PR merges.
Suite-health, throughput, top-failing and top-flaky leaderboards, coverage trends, and a release-readiness verdict — with CSV export.
Two-way sync with Jira, GitLab, Azure DevOps, plus Slack notifications and GitHub — connect in one click, no tokens.
A test fails in CI, an agent spots an anomaly, or a QA engineer flags a risk. All paths lead to a Finding with full evidence.
Claude reads the finding, checks for duplicates, suggests a severity, drafts a fix plan, and optionally opens a pull request.
The PR merges. OMGQA detects it and moves the finding to Ready for retest, the sprint velocity updates, the team is notified.
OMG QA exposes 14 governed MCP tools so any agent can create, search, and triage findings programmatically — without leaving their context. See the MCP guide →
// Claude Code — check for duplicates first
const dupes = await mcp.call("find_similar_findings", {
projectKey: "CHK",
title: "Payment sheet hangs after 3DS timeout",
});
// Claude Code — file the finding via MCP
const finding = await mcp.call("create_finding", {
projectKey: "CHK",
title: "Payment sheet hangs after 3DS timeout",
type: "bug",
severity: "critical",
});
// Human reviews, then an agent moves it forward
await mcp.call("transition_finding", {
findingId: finding.id,
status: "in_progress",
});
Every failure is auto-classified into a 7-category taxonomy — product bug, UI timing, environment, data/parallelism, flaky, suite config, or unknown — by a deterministic rules engine with an optional AI classifier. A reviewer's correction is remembered and biases future runs.