Billing
Pend 0Skip 0Runs 2
2
0.26%
0.26%
756
Executive Snapshot
7
Daily Runs
2/7
Daily Green
22m 06s
Avg Daily Runtime
19
Smoke Attempts
17/19
Smoke Green
2m 55s
Avg Smoke Runtime
3m 03s
Median Smoke Time
2
Current Green Streak
Executive Analysis
Bottom line: the regression system is informative but not calm. The data suggest repeatable problem areas rather than random breakage, which means focused ownership should move the needle quickly.
What Matters
- Daily regression passed 2 of 7 runs (28.6%), with a current green streak of 2 and a best streak of 2 in this window.
- Smoke passed 17 of 19 attempts (89.5%) across 14 production pipelines. 1 pipeline(s) recovered on rerun, which is useful for continuity but also a sign that first-pass deploy signal is noisier than it should be. 1 failed attempt(s) never reached test execution counts at all.
- Failure concentration is not random: Web has the highest strict failure ratio at 0.27%, while Web has the broadest non-pass footprint at 0.27%.
- Frontend is the weakest smoke surface in this window at 12/14 green (85.7%).
- Daily-suite runtime averaged 22m 06s.
Engineering Analysis
- A release gate should fail loudly for product regressions and quietly for infrastructure noise. Rerun recoveries plus incomplete daily or smoke attempts suggest those two failure modes are still partially mixed together.
- The failure profile is concentrated enough to act on. Web and Web are carrying the strongest signal, which means reliability work should be assigned by category ownership instead of treating the suite as one undifferentiated problem.
- The broader daily suite is carrying more instability than smoke, which usually means product regressions are escaping into wider coverage areas even when the narrow deploy gate looks acceptable.
Recommended Actions
- Split incomplete execution failures from real assertion failures in the report narrative. Setup breakage should stay visible, but it should not look identical to a product regression in the executive readout.
- Assign one owner to Web for the next cycle and expect a short written burn-down: top failing tests, suspected root causes, flake versus regression breakdown, and what gets fixed or quarantined first.
- Treat the daily regression suite like an operations queue until it is calm again: triage failures after each red run, close known-noise items fast, and avoid letting multiple unrelated red signals pile up between runs.
- Put Frontend smoke under closer guardrails for the next release cycle. It is the best place to improve first-pass deploy confidence quickly.
Improvement Ideas
- Introduce a small reliability budget for tests: every flaky or quarantined case needs an owner and an expiry, and the team should review that budget weekly the same way it reviews bugs or incidents.
- Track first-fail to root-cause time as a core metric. Fast diagnosis is as important as raw pass rate because the practical value of a test gate depends on how quickly it helps the team recover.
- Define a runtime budget per suite and require justification when test count or duration grows. Reliable feedback systems stay trusted when they remain both stable and proportionate.
Category Execution Ratios
How computed
Category total executions means the sum of that category's observed test executions across every daily-suite run in the selected window.
Strict Failure Ratio = failed executions for that category divided by total executions for that category across the window.
Non-pass Ratio = (failed + pending + skipped) executions for that category divided by total executions for that category across the window.
Example: if Billing executed 800 times across the week and 2 of those executions failed, Billing strict failure ratio is 0.25%. That does not mean 0.25% of pipelines failed; it means 0.25% of observed Billing executions ended in failed.
How computed
Category total executions means the sum of that category's observed test executions across every daily-suite run in the selected window.
Strict Failure Ratio = failed executions for that category divided by total executions for that category across the window.
Non-pass Ratio = (failed + pending + skipped) executions for that category divided by total executions for that category across the window.
Example: if Billing executed 800 times across the week and 2 of those executions failed, Billing strict failure ratio is 0.25%. That does not mean 0.25% of pipelines failed; it means 0.25% of observed Billing executions ended in failed.
Strict Failure Ratio
Share of category executions that ended in failed across all daily runs in this window.
Billing0.26%
Web0.27%
Frontend0.26%
Library0.00%
Non-pass Ratio
Share of category executions that ended in failed, pending, or skipped across all daily runs in this window.
Billing0.26%
Web0.27%
Frontend0.26%
Library0.00%
Category Aggregate Table
How computed
Category total executions means the sum of that category's observed test executions across every daily-suite run in the selected window.
Strict Failure Ratio = failed executions for that category divided by total executions for that category across the window.
Non-pass Ratio = (failed + pending + skipped) executions for that category divided by total executions for that category across the window.
Example: if Billing executed 800 times across the week and 2 of those executions failed, Billing strict failure ratio is 0.25%. That does not mean 0.25% of pipelines failed; it means 0.25% of observed Billing executions ended in failed.
How computed
Category total executions means the sum of that category's observed test executions across every daily-suite run in the selected window.
Strict Failure Ratio = failed executions for that category divided by total executions for that category across the window.
Non-pass Ratio = (failed + pending + skipped) executions for that category divided by total executions for that category across the window.
Example: if Billing executed 800 times across the week and 2 of those executions failed, Billing strict failure ratio is 0.25%. That does not mean 0.25% of pipelines failed; it means 0.25% of observed Billing executions ended in failed.
| Category | Total | Failed | Pending | Skipped | Failure Ratio | Non-pass Ratio | Runs With Failures |
|---|---|---|---|---|---|---|---|
| Billing | 756 | 2 | 0 | 0 | 0.26% | 0.26% | 2 |
| Web | 5460 | 15 | 0 | 0 | 0.27% | 0.27% | 5 |
| Frontend | 1890 | 5 | 0 | 0 | 0.26% | 0.26% | 5 |
| Library | 602 | 0 | 0 | 0 | 0.00% | 0.00% | 0 |
CatFailF%NP%Tot
Web
Pend 0Skip 0Runs 5
15
0.27%
0.27%
5460
Frontend
Pend 0Skip 0Runs 5
5
0.26%
0.26%
1890
Library
Pend 0Skip 0Runs 0
0
0.00%
0.00%
602
Recent Runs
Recent Daily Suite Runs
| Date | Pipeline | Suites | Status | Summary |
|---|---|---|---|---|
| 2026-04-18 18:25 | 152618 | BillingWebFrontendLibrary | FAILED | Total 1244 | Passed 1239 | Failed 5 |
| 2026-04-19 18:25 | 152660 | BillingWebFrontendLibrary | FAILED | Total 1244 | Passed 1239 | Failed 5 |
| 2026-04-20 18:25 | 152815 | BillingWebFrontendLibrary | FAILED | Total 1244 | Passed 1240 | Failed 4 |
| 2026-04-21 18:25 | 152943 | BillingWebFrontendLibrary | FAILED | Total 1244 | Passed 1240 | Failed 4 |
| 2026-04-22 18:25 | 153127 | BillingWebFrontendLibrary | FAILED | Total 1244 | Passed 1240 | Failed 4 |
| 2026-04-23 18:25 | 153307 | BillingWebFrontendLibrary | PASSED | Total 1244 | Passed 1244 | Failed 0 |
| 2026-04-24 18:24 | 153522 | BillingWebFrontendLibrary | PASSED | Total 1244 | Passed 1244 | Failed 0 |
FAILED
T 1244 | P 1239 | F 5 | Pend 0
FAILED
T 1244 | P 1239 | F 5 | Pend 0
FAILED
T 1244 | P 1240 | F 4 | Pend 0
FAILED
T 1244 | P 1240 | F 4 | Pend 0
FAILED
T 1244 | P 1240 | F 4 | Pend 0
PASSED
T 1244 | P 1244 | F 0 | Pend 0
PASSED
T 1244 | P 1244 | F 0 | Pend 0
Recent Smoke Attempts
| Date | Suite | Pipeline | Job | Status | Passed | Failed | Duration |
|---|---|---|---|---|---|---|---|
| 2026-04-20 13:44 | Frontend | 152756 | Frontend smoke | FAILED | 109 | 1 | 3m 51s |
| 2026-04-20 14:17 | Frontend | 152769 | Frontend smoke | PASSED | 110 | 0 | 3m 10s |
| 2026-04-20 16:27 | Frontend | 152805 | Frontend smoke | PASSED | 110 | 0 | 3m 10s |
| 2026-04-20 17:10 | University | 152805 | University smoke | PASSED | 60 | 0 | 2m 34s |
| 2026-04-20 18:27 | Frontend | 152817 | Frontend smoke | PASSED | 110 | 0 | 3m 22s |
| 2026-04-21 14:08 | Frontend | 152911 | Frontend smoke | FAILED | n/a | n/a | 0m 02s |
| 2026-04-21 14:15 | University | 152911 | University smoke | PASSED | 60 | 0 | 2m 50s |
| 2026-04-22 12:12 | Frontend | 153013 | Frontend smoke | PASSED | 110 | 0 | 3m 43s |
| 2026-04-22 16:54 | Frontend | 153119 | Frontend smoke | PASSED | 110 | 0 | 3m 03s |
| 2026-04-23 15:06 | University | 153256 | University smoke | PASSED | 60 | 0 | 2m 51s |
| 2026-04-23 15:08 | Frontend | 153256 | Frontend smoke | PASSED | 110 | 0 | 3m 43s |
| 2026-04-23 17:40 | Frontend | 153296 | Frontend smoke | PASSED | 110 | 0 | 3m 06s |
| 2026-04-23 17:46 | University | 153296 | University smoke | PASSED | 60 | 0 | 2m 14s |
| 2026-04-23 18:01 | Frontend | 153305 | Frontend smoke | PASSED | 110 | 0 | 3m 02s |
| 2026-04-24 13:04 | Frontend | 153427 | Frontend smoke | PASSED | 110 | 0 | 3m 16s |
| 2026-04-24 13:20 | Frontend | 153452 | Frontend smoke | PASSED | 110 | 0 | 2m 59s |
| 2026-04-24 14:51 | Frontend | 153482 | Frontend smoke | PASSED | 110 | 0 | 3m 21s |
| 2026-04-24 16:17 | University | 153512 | University smoke | PASSED | 60 | 0 | 2m 07s |
| 2026-04-24 16:21 | Frontend | 153512 | Frontend smoke | PASSED | 110 | 0 | 2m 59s |
FAILED
P 109 | F 1 | 3m 51s
PASSED
P 110 | F 0 | 3m 10s
PASSED
P 110 | F 0 | 3m 10s
PASSED
P 60 | F 0 | 2m 34s
PASSED
P 110 | F 0 | 3m 22s
FAILED
P n/a | F n/a | 0m 02s
PASSED
P 60 | F 0 | 2m 50s
PASSED
P 110 | F 0 | 3m 43s
PASSED
P 110 | F 0 | 3m 03s
PASSED
P 60 | F 0 | 2m 51s
PASSED
P 110 | F 0 | 3m 43s
PASSED
P 110 | F 0 | 3m 06s
PASSED
P 60 | F 0 | 2m 14s
PASSED
P 110 | F 0 | 3m 02s
PASSED
P 110 | F 0 | 3m 16s
PASSED
P 110 | F 0 | 2m 59s
PASSED
P 110 | F 0 | 3m 21s
PASSED
P 60 | F 0 | 2m 07s
PASSED
P 110 | F 0 | 2m 59s
Smoke Suite Breakdown
Frontend
14 attempts across 14 pipelines
Passed12
Failed2
Incomplete1
Avg runtime3m 03s
Median passing runtime3m 10s
Pipelines14
University
5 attempts across 5 pipelines
Passed5
Failed0
Incomplete0
Avg runtime2m 31s
Median passing runtime2m 34s
Pipelines5