# Nightly Test Summary — 2026-07-02

**⚠️ ANOMALY — ALL 1606 TESTS SKIPPED, 0 PASSED, 0 FAILED. Suite did not actually execute.**

## Verdict
Not a per-test regression — the entire run produced zero pass/fail results. Every test in every spec file came back `status: "skipped"` with an empty `results: []` array, meaning Playwright never ran the test bodies at all. Prior nightly runs (baseline 2026-06-20) had 0 failed with ~1034 tests actually passing; tonight 0 tests passed.

## Numbers
- Total: 1606
- Passed (expected): 0
- Failed (unexpected): 0
- Skipped: 1606
- Flaky: 0
- Errors array: empty (no top-level Playwright error captured)
- Exit code (marker): 0
- Duration: ~1283s (~21 min)
- Projects: android-chrome, desktop-chrome (36 suites)

## Regression vs baseline
Baseline (`project_pwa_test_coverage.md`, 2026-06-20): ~1220+ total, 186 skipped, 0 failed (~1034 passed).
Tonight: 1606 total, 1606 skipped (100%), 0 passed.

**This is a regression** — going from ~1034 passing tests to 0 passing tests, with no failures and no captured errors, points to a suite-level cause (e.g. dev server/BASE_URL unreachable during the 01:00 IST run window, or a global skip condition tripping for every test) rather than individual test breakage. Sample spec (`activity.spec.js`, "page or hub loads") shows the pattern: test present, `expectedStatus: "passed"`, but `results: []` and `status: "skipped"` — consistent with every test's runtime skip-guard (e.g. `siteIsOk()`/`isBuilt()`-style checks per `feedback_test_skip_patterns.md`) evaluating false because the target server was not reachable, not with individual test logic failing.

## Known skip-gated specs (expected to skip regardless)
Per `feedback_test_skip_patterns.md`: `_template.spec.js`, `health_smoke.spec.js`, `mappls-creds.spec.js`, `custodian_tutorial_screenshots.spec.js`, `custodian_s9_recording.spec.js`, `yagya-portfolio.spec.js`, and structure tests in `client.spec.js`. These normally account for the baseline's 186 skips — not the other ~1420 tests skipped tonight.

## Failing spec files/titles
None — 0 unexpected/failed. (No failures to list; every test is `skipped`, not `failed`.)

## Action needed
Investigate why the target app was unreachable (or why skip-guards fired) during the 2026-07-02 01:00 IST nightly window before trusting the next nightly run. Do not treat tonight's "0 failed" as a clean bill of health.