new relic.

Dunning & Collections QA Tracker

Snapshot 2026-10-29T16:53:50.111Z

1 Summary

Project: (parent )

2 Test Execution Results

Total test iterations and results by the numbers — every figure in this section counts iterations, not test cases. Defect data is reported separately in Section 3.

Test Results by the Numbers

3 Defect Summary

Defects filed against this project: severe-defect highlight and scannable metrics by status, severity and functional area.

Total Defect Open by Priority

Open defects only, split by Jira priority. Resolved defects are excluded.

By status

By severity

Open defects

Failure Type

What kind of failure QA is finding, independent of which surface it was found on.

4 Functional-Area Coverage

Ticket coverage across the Dunning workflow surfaces.

Where the bugs are

Defect volume per functional area — the further the shape reaches, the more bugs QA has found on that surface.

Coverage across the paywall journey

Each ring segment is one functional area's share of the in-scope tickets; red marks where defects were found, grey means none. The chain shows the enforcement states this suite exercises.

5 Scope

In scope

Derived from the tickets linked to the test plan — this list cannot drift out of sync with Jira.

Out of scope

    Dunning Process · Invoice-to-Cash QA program · built for internal program tracking
    🔒 NEW RELIC CONFIDENTIAL · INTERNAL USE ONLY
    Source: Jira & Xray
    auto-refresh · every 6 hours
    Prepared by finance-boba-frameworks-qa Team