Billing
Pend 0Skip 0Runs 0
0
0.00%
0.00%
756
Executive Snapshot
7
Daily Runs
4/7
Daily Green
19m 43s
Avg Daily Runtime
21
Smoke Attempts
12/21
Smoke Green
3m 21s
Avg Smoke Runtime
3m 03s
Median Smoke Time
2
Current Green Streak
Executive Analysis
Bottom line: release confidence is unstable in both the broad regression path and the deploy smoke path. The immediate job is to separate real product regressions from execution noise, then burn down the concentrated failure clusters.
What Matters
- Daily regression passed 4 of 7 runs (57.1%), with a current green streak of 2 and a best streak of 2 in this window.
- Smoke passed 12 of 21 attempts (57.1%) 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. 2 failed attempt(s) never reached test execution counts at all.
- Failure concentration is not random: Frontend has the highest strict failure ratio at 0.68%, while Frontend has the broadest non-pass footprint at 0.68%.
- University is the weakest smoke surface in this window at 0/4 green (0.0%).
- Daily-suite runtime averaged 19m 43s, while observed daily test volume moved from 1,188 to 1,189.
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. Frontend and Frontend are carrying the strongest signal, which means reliability work should be assigned by category ownership instead of treating the suite as one undifferentiated problem.
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 Frontend 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 University 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.00%
Web0.04%
Frontend0.68%
Library0.00%
Non-pass Ratio
Share of category executions that ended in failed, pending, or skipped across all daily runs in this window.
Billing0.00%
Web0.04%
Frontend0.68%
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 | 0 | 0 | 0 | 0.00% | 0.00% | 0 |
| Web | 5201 | 2 | 0 | 0 | 0.04% | 0.04% | 2 |
| Frontend | 1759 | 12 | 0 | 0 | 0.68% | 0.68% | 3 |
| Library | 602 | 0 | 0 | 0 | 0.00% | 0.00% | 0 |
CatFailF%NP%Tot
Web
Pend 0Skip 0Runs 2
2
0.04%
0.04%
5201
Frontend
Pend 0Skip 0Runs 3
12
0.68%
0.68%
1759
Library
Pend 0Skip 0Runs 0
0
0.00%
0.00%
602
Recent Runs
Recent Daily Suite Runs
| Date | Pipeline | Suites | Status | Summary |
|---|---|---|---|---|
| 2026-03-14 18:22 | 148497 | BillingWebFrontendLibrary | PASSED | Total 1188 | Passed 1188 | Failed 0 |
| 2026-03-15 18:23 | 148499 | BillingWebFrontendLibrary | PASSED | Total 1188 | Passed 1188 | Failed 0 |
| 2026-03-16 18:23 | 148604 | BillingWebFrontendLibrary | FAILED | Total 1188 | Passed 1187 | Failed 5 |
| 2026-03-17 18:22 | 148823 | BillingWebFrontendLibrary | FAILED | Total 1188 | Passed 1188 | Failed 4 |
| 2026-03-18 18:22 | 149034 | BillingWebFrontendLibrary | FAILED | Total 1188 | Passed 1187 | Failed 5 |
| 2026-03-19 18:24 | 149182 | BillingWebFrontendLibrary | PASSED | Total 1189 | Passed 1189 | Failed 0 |
| 2026-03-20 18:22 | 149392 | BillingWebFrontendLibrary | PASSED | Total 1189 | Passed 1189 | Failed 0 |
PASSED
T 1188 | P 1188 | F 0 | Pend 0
PASSED
T 1188 | P 1188 | F 0 | Pend 0
FAILED
T 1188 | P 1187 | F 5 | Pend 0
FAILED
T 1188 | P 1188 | F 4 | Pend 0
FAILED
T 1188 | P 1187 | F 5 | Pend 0
PASSED
T 1189 | P 1189 | F 0 | Pend 0
PASSED
T 1189 | P 1189 | F 0 | Pend 0
Recent Smoke Attempts
| Date | Suite | Pipeline | Job | Status | Passed | Failed | Duration |
|---|---|---|---|---|---|---|---|
| 2026-03-16 21:17 | Frontend | 148625 | Frontend smoke | PASSED | 110 | 0 | 3m 03s |
| 2026-03-16 21:49 | Frontend | 148633 | Frontend smoke | PASSED | 110 | 0 | 3m 02s |
| 2026-03-16 22:08 | Frontend | 148635 | Frontend smoke | PASSED | 110 | 0 | 2m 58s |
| 2026-03-16 22:38 | Frontend | 148640 | Frontend smoke | PASSED | 110 | 0 | 3m 00s |
| 2026-03-16 22:59 | Frontend | 148644 | Frontend smoke | PASSED | 110 | 0 | 2m 57s |
| 2026-03-16 23:53 | Frontend | 148646 | Frontend smoke | PASSED | 110 | 0 | 3m 00s |
| 2026-03-17 00:06 | Frontend | 148648 | Frontend smoke | PASSED | 110 | 0 | 3m 03s |
| 2026-03-17 00:24 | Frontend | 148651 | Frontend smoke | PASSED | 110 | 0 | 3m 03s |
| 2026-03-17 12:06 | Frontend | 148704 | Frontend smoke | PASSED | 110 | 0 | 3m 04s |
| 2026-03-17 16:09 | Frontend | 148791 | Frontend smoke | PASSED | 110 | 0 | 3m 04s |
| 2026-03-17 16:56 | Frontend | 148817 | Frontend smoke | PASSED | 110 | 0 | 3m 09s |
| 2026-03-18 12:28 | University | 148817 | University smoke | FAILED | n/a | n/a | 0m 02s |
| 2026-03-18 12:28 | University | 148817 | University smoke | FAILED | n/a | n/a | 0m 02s |
| 2026-03-18 16:49 | Frontend | 149024 | Frontend smoke | PASSED | 110 | 0 | 3m 10s |
| 2026-03-20 13:16 | Frontend | 149311 | Frontend smoke | FAILED | 0 | 4 | 2m 13s |
| 2026-03-20 13:19 | Frontend | 149311 | Frontend smoke | FAILED | 0 | 4 | 2m 06s |
| 2026-03-20 13:30 | Frontend | 149311 | Frontend smoke | FAILED | 0 | 4 | 2m 13s |
| 2026-03-20 13:36 | University | 149311 | University smoke | FAILED | 0 | 60 | 21m 11s |
| 2026-03-20 17:03 | Frontend | 149382 | Frontend smoke | FAILED | 0 | 4 | 1m 26s |
| 2026-03-20 17:06 | University | 149382 | University smoke | FAILED | 57 | 3 | 3m 38s |
| 2026-03-20 17:13 | Frontend | 149382 | Frontend smoke | FAILED | 0 | 1 | 0m 48s |
PASSED
P 110 | F 0 | 3m 03s
PASSED
P 110 | F 0 | 3m 02s
PASSED
P 110 | F 0 | 2m 58s
PASSED
P 110 | F 0 | 3m 00s
PASSED
P 110 | F 0 | 2m 57s
PASSED
P 110 | F 0 | 3m 00s
PASSED
P 110 | F 0 | 3m 03s
PASSED
P 110 | F 0 | 3m 03s
PASSED
P 110 | F 0 | 3m 04s
PASSED
P 110 | F 0 | 3m 04s
PASSED
P 110 | F 0 | 3m 09s
FAILED
P n/a | F n/a | 0m 02s
FAILED
P n/a | F n/a | 0m 02s
PASSED
P 110 | F 0 | 3m 10s
FAILED
P 0 | F 4 | 2m 13s
FAILED
P 0 | F 4 | 2m 06s
FAILED
P 0 | F 4 | 2m 13s
FAILED
P 0 | F 60 | 21m 11s
FAILED
P 0 | F 4 | 1m 26s
FAILED
P 57 | F 3 | 3m 38s
FAILED
P 0 | F 1 | 0m 48s
Smoke Suite Breakdown
Frontend
17 attempts across 14 pipelines
Passed12
Failed5
Incomplete0
Avg runtime2m 40s
Median passing runtime3m 03s
Pipelines14
University
4 attempts across 3 pipelines
Passed0
Failed4
Incomplete2
Avg runtime6m 13s
Median passing runtimen/a
Pipelines3