VALIDATION LAB•REPORTS
Reports
Runs · Bugs · Evidence — the full audit trail behind every release. Use the in-page anchors to jump between the dashboard, counters, screenshot gallery, video logs, the bug report generator, and a Jira-shaped ticket example.
01 · Pass / Fail Counters
The first thing a release manager looks at
Pass rate (24h)
50.0%
rolling 7d 99.1%
Specs ran
412
6 this hour
Failed
1
1 sev-2 · 0 sev-1
Flaky
1
auto-quarantined
Running
1
live shard 2/4
02 · Test Result Dashboard
Filterable run history with full audit trail
| Run | Spec | Branch | Shard | Duration | Status | When |
|---|---|---|---|---|---|---|
| VL-7421 | checkout.three-step-happy-path | main | 3/4 | 00:42 | Passed | 12 min ago |
| VL-7420 | wallet.deposit-validation | main | 1/4 | 00:18 | Passed | 12 min ago |
| VL-7419 | auth.session-timeout | feat/jwt-refresh | 2/4 | 01:06 | Flaky | 28 min ago |
| VL-7418 | admin.export-csv | main | 4/4 | 00:09 | Failed | 1 hr ago |
| VL-7417 | scenarios.race-conditions | main | 2/4 | 00:51 | Running | just now |
| VL-7416 | practice.iframes | main | 1/4 | 00:14 | Passed | 2 hr ago |
03 · Screenshot Evidence
Captured on failure, attached to the run
checkout.three-step — Step 3
Pass · trace cap 3.4 MB · 1 retry
wallet.pending — settlement
Pass · 1 deposit posted in 2.1 s
admin.export-csv — failure
Fail · download.suggestedFilename mismatch
auth.session-timeout — flaky
Flaky · 1 of 3 retries succeeded
04 · Video Run Logs
Replay the failure, frame-accurate
VL-7418
Failed- 00:01 — page.goto('/users')
- 00:03 — getByRole('button', { name: /export csv/i }).click()
- 00:07 — assertion failed: filename did not match contract
VL-7419
Flaky- 00:00 — login(demo)
- 00:18 — wallet route mounted
- 00:42 — flake retry 1: localStorage cleared late
- 01:06 — retry 2 passed
05 · Bug Report Generator
Convert a tester's notes into a senior-grade ticket
1234567891011121314151617181920
### Checkout Place Order fires twice on slow networks
**Severity:** Sev-2
**Module:** scenarios/checkout
**Steps to reproduce**
1. Sign in with demo credentials
2. Open /checkout, fill shipping + 4242 card
3. Click Place Order with throttle = Slow 3G
4. Observe two POST /orders calls in DevTools
**Expected**
Place Order should be disabled after first click; idempotency-key prevents the second order.
**Actual**
Two orders created with distinct order IDs; the user is double-charged.
Markdown preview
### Checkout Place Order fires twice on slow networks **Severity:** Sev-2 **Module:** scenarios/checkout **Steps to reproduce** 1. Sign in with demo credentials 2. Open /checkout, fill shipping + 4242 card 3. Click Place Order with throttle = Slow 3G 4. Observe two POST /orders calls in DevTools **Expected** Place Order should be disabled after first click; idempotency-key prevents the second order. **Actual** Two orders created with distinct order IDs; the user is double-charged.
06 · Jira Ticket Example
What a senior QA actually files
Checkout Place Order fires twice on Slow 3G
Customers on throttled connections create a duplicate order whenever Place Order is clicked. The second order is also charged. No idempotency-key on the request.
Steps:
1. Sign in (demo) · 2. /checkout, fill shipping + 4242 card · 3. Place Order with throttle Slow 3G · 4. Inspect POST /api/orders in DevTools.
Expected: Place Order disabled after first click; idempotency-key prevents the second order.
Actual: Two orders VL-AB12CD + VL-AB12CE; customer double-charged.
Risk if shipped
Revenue impact + chargeback storms + trust hit. Recommend hotfix branch + idempotency-key in 24h.