Reporting & Quality
Defect Tracking
A defect is a bug tracked within Qualflare, linked directly to the test case and run that found it — so verifying a fix means re-running the actual test, not just trusting that someone checked.
Product news and testing tips.
Why it matters
A bug found in testing, filed nowhere
A test fails, someone notices, and the bug lives in a Slack thread until someone remembers to file it properly — if they do.
No link between the bug and the test that found it
The defect tracker and the test results live in different tools, so “is this actually fixed” means manually checking both.
Severity is a vibe, not a definition
One engineer's “critical” is another's “medium.” Without shared definitions, triage prioritization is inconsistent across the team.
How it works
File a defect from a failed test result, assign a severity and owner, and track it through Open → In Progress → Resolved → Closed. Re-run the linked test to verify the fix — the test passing again is what closes the loop.
QualflareDefects
| Name | Severity | Created | Status |
|---|---|---|---|
#84Login redirect fails after SSO timeout | critical | Mar 27 | Active |
#83Null pointer in user profile serialization | high | Mar 26 | Action required |
#82Payment webhook retry exceeds max attempts | critical | Mar 25 | Active |
#81Dashboard chart flickers on data refresh | medium | Mar 24 | False positive |
#80CSV export truncates unicode characters | high | Mar 23 | Reopened |
#79Mobile nav overlay blocks scroll on iOS | medium | Mar 21 | Closed |
#78API rate limiter resets counter prematurely | high | Mar 20 | Active |
#77File upload progress bar stuck at 99% | low | Mar 18 | Closed |
What you get
File a defect straight from a failure
Create a defect directly from a failed test result, pre-linked to the case and run that found it — no re-typing what already failed.
Fix verification, closed-loop
Re-run the linked test to verify a fix. Bug discovery, tracking, verification, and closing the loop stay connected through the whole lifecycle.
Defined severity levels
Critical, High, Medium, and Low each ship with concrete examples, so triage means the same thing across the team instead of a gut call.
Two-way sync with GitHub or GitLab
A defect created in Qualflare creates a linked GitHub or GitLab Issue automatically, and closing or reopening one side does the same on the other.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
Frequently asked questions
What is a defect in Qualflare?
A defect is a bug or issue found during testing that's tracked within Qualflare, with a lifecycle from Open through In Progress to Resolved and Closed (with a Reopened branch if a fix doesn't hold).
How does defect severity work?
Four levels, each with concrete examples: Critical (system unusable, data loss, security breach — e.g. login completely broken), High (a major feature broken, e.g. checkout fails half the time), Medium (a minor feature with an easy workaround, e.g. sorting in the wrong order), and Low (cosmetic, e.g. a misspelled label).
Can defects sync with Jira, GitHub, or GitLab?
Yes. GitHub and GitLab sync two ways — a defect created in Qualflare creates a linked Issue, and closing or reopening either side updates the other. Jira integration creates linked issues from defects, with status syncing into Jira.
How does fix verification work?
The loop is: a test fails and a defect is created, the defect tracks fix progress, you re-run the linked test to verify the fix, and the test passing closes the defect — so “fixed” means the test actually passes again, not just that someone said so.