Defect Tracking

When a test fails, you need to capture it, route it, and fix it without copying details between tools. Defect Tracking lets you log defects where the failure happened and keeps each one tied to the run that produced it. Your team works the issue in the tools they already use.

Who it’s for#

Testers and engineers who raise and resolve defects, and the leads who triage them and watch them through to closed.

What it does#

• Log and manage — record defects with the context needed to reproduce and fix them.
• Triage — sort, prioritize, and assign so the right work surfaces first.
• Comments — discuss a defect in place, keeping the conversation next to the evidence.
• Run linkage — every defect links back to the test run that found it.
• External trackers — push a defect to your existing issue tracker through integrations.

How it works#

You raise a defect from a failed run, and it carries the run reference with it. From there you triage, comment, and assign. If your team lives in another issue tracker, the defect flows there so nobody has to re-enter it.

Why it matters#

A defect without its test run is a guess. Keeping the link intact means anyone picking up the issue can see exactly what failed and how to reproduce it, which shortens the path from report to fix.