# Nightly Test Summary — 2026-07-02 run (finished 2026-07-03 05:44 IST)

**REGRESSIONS — 962/1632 tests failed (59%), up from 0 failed in the 2026-06-20 baseline. Failure pattern (404s on manifest.json, 406s from PostgREST across unrelated PWAs, whole-file 100% failure on printing/vendors/customers/stores/yagya-portfolio) points to a systemic outage during the run — server/DB/proxy down or unreachable — not per-PWA code regressions.**

## Totals
- Total: 1632
- Passed: 538
- Failed: 962
- Skipped: 132
- Flaky: 0
- Marker: date=20260702 (UTC start-day label — server TZ is UTC, run actually executed IST night of 07-02→07-03), exit_code=1
- Run window: startTime 2026-07-02T18:45:03Z (00:15 IST Jul 3) → finished_at 2026-07-03T00:14:11Z (05:44 IST Jul 3) — ~5.5hr duration

## Failures by spec file (all counted as regressions vs baseline's 0 failed)
| Spec file | Failed / Total |
|---|---|
| fundcustodian.spec.js | 154/176 |
| printing.spec.js | 94/94 |
| sales_billing.spec.js | 82/96 |
| vendors.spec.js | 74/74 |
| counters.spec.js | 68/86 |
| upi_pay.spec.js | 68/76 |
| customers.spec.js | 50/50 |
| recce.spec.js | 44/150 |
| custodian.spec.js | 40/80 |
| hr.spec.js | 36/38 |
| sales.spec.js | 34/44 |
| safe_bottom.spec.js | 28/78 |
| stores.spec.js | 26/26 |
| vehicle.spec.js | 20/22 |
| yagya-portfolio.spec.js | 18/18 |
| expense.spec.js | 16/18 |
| contacts.spec.js | 14/16 |
| finance.spec.js | 10/12 |
| installation.spec.js | 10/12 |
| learn.spec.js | 10/12 |
| tour_planner.spec.js | 10/12 |
| hub.spec.js | 8/30 |
| oc_admin.spec.js | 8/10 |
| production.spec.js | 8/10 |
| vrs.spec.js | 8/10 |
| admin.spec.js | 6/38 |
| recce_client.spec.js | 6/48 |
| smoke.spec.js | 6/34 |
| client.spec.js | 4/46 |
| debug_tour.spec.js | 2/2 |

## Sample failing tests (first 20 of 962)
- admin.spec.js :: client.zones table exists and is accessible via PostgREST (Expected 200, received 406)
- admin.spec.js :: client.accounts has zone and is_head columns (Expected 200, received 406)
- admin.spec.js :: installation.campaigns has zones column (Expected 200, received 406)
- client.spec.js :: manifest.json returns 200 (Expected 200, received 404)
- client.spec.js :: sw.js contains current 360client version (received HTML doctype instead of JS — likely a 404/error page)
- contacts.spec.js :: manifest.json returns 200
- contacts.spec.js :: sw.js is versioned
- contacts.spec.js :: auth screen and app container present
- contacts.spec.js :: hub navigation button present
- contacts.spec.js :: search and contact list elements present
- contacts.spec.js :: Dexie offline DB used
- contacts.spec.js :: Top Management access control in place
- (full list of 962 failures available in test_reports/nightly_20260702.json)

## Notes
- Error signatures (406 from PostgREST, 404/HTML instead of JS for manifest/sw.js) are consistent across totally unrelated PWAs — strong evidence the app server, PostgREST, or reverse proxy was unavailable/misconfigured for some or all of this run's window, rather than 962 independent app bugs.
- Recommend re-running the suite manually against a confirmed-up dev environment before treating any individual failure as a real regression.
- Baseline (project_pwa_test_coverage.md) updated below to reflect this run's counts, with a flag that root cause needs investigation.