@unotest/viewer 0.18.0 → 0.20.0

package/CHANGELOG.md

@@ -1,5 +1,140 @@
 # Changelog
 
+## [0.20.0] - 2026-08-24
+
+### Minor Changes
+
+- 7957469: A status of its own for tests that are supposed to fail, and tiles that fade with age.
+
+  **`// @expect-fail`.** A scenario can declare that failing IS its assertion.
+  The marker lives in the comment block before the first code — with the
+  mandatory header (right after the colour line) or without one. The parser is
+  `parseScenarioAnnotations` in `@unotest/protocol`; `ScenarioMeta` gains an
+  `expectFail` field.
+
+  Such a scenario carries its own status in the viewer (`expected`, purple):
+  it stays out of the FAILED counter, out of the "failing now" badge and out
+  of the "Failing now" section. The inverse case — a marked test that
+  **passed** — turns red: whatever it was guarding stopped breaking and nobody
+  found out. One rule (`scenarioHealthStatus`) drives the dashboard, the
+  scenario tree and the badge, so the three cannot drift apart.
+
+  The runner does not interpret the marker: exit code and run status are
+  unchanged. The run really did fail — it is the test itself that is fine.
+
+  **Fading.** An overview tile dims as its last result ages: four steps (hour /
+  day / week / older) set the strength of the fill itself — 46 / 30 / 19 / 11%
+  of the status colour. The 11% floor keeps an old red still red. The time of
+  the last run is now part of the tile's accessible name — colour is the one
+  channel a screen reader does not have.
+
+### Patch Changes
+
+- aab65a5: A failure in the first test of a file is no longer lost, and the dashboard no longer waits for F5.
+
+  **One run, one `run:finished`.** The event was written by the executor's
+  per-entry tap, so a file with four `test_*()` functions left four terminal
+  events in `steps.jsonl`. Every consumer reads the last one — so `collection`
+  reported a scenario green whenever the final function passed and the first
+  one failed. The runner now writes the event once, folding the outcomes of
+  every entry: `failed` > `interrupted` > `aborted` > `completed`. A run that
+  never got started (no entry function, browser failed to launch) writes a
+  terminal event too — its artifact used to read as "the process died".
+
+  **The viewer asks for the index again.** The first `load()` could land while
+  the server was still rebuilding the run index: the answer was "no runs", and
+  nobody asked again — WS only reports a run starting and finishing. On a
+  project with history the whole overview showed "never run" until a page
+  reload. `indexReady: false` now schedules a retry with a 0.5s → 30s backoff,
+  until the first ready answer.
+
+- Updated dependencies [7957469]
+- Updated dependencies [c6efd92]
+  - @unotest/protocol@0.20.0
+  - @unotest/dsl@0.20.0
+
+## [0.19.0] - 2026-08-23
+
+### Minor Changes
+
+- dfb3991: Per-collection parallelism via a `workers:` field in the collection YAML.
+
+  - `workers: N` (integer ≥ 1) in `unotest/e2e/_collections/*.yaml` sets how
+    many scenarios of that collection run concurrently; omitted = serial.
+  - Precedence: CLI `--workers=N` flag > manifest `workers:` > 1.
+  - Viewer: the collection header shows an editable `workers` value; the
+    setting is stored in the YAML, so CLI and CI runs pick it up too.
+  - `CollectionMeta` (protocol) gains a `workers: number | null` field.
+
+- Run history scales: runs are filed under daily shards and the viewer stops
+  polling history it is not showing.
+
+  - New on-disk layout `unotest/.runs/<YYYY>/<MM>/<DD>/<runId>/` (UTC date the
+    run started). The shard is a pure function of the `runId`, which already
+    carries the timestamp — a direct link to a run keeps working even with the
+    index deleted. Existing flat `.runs/<runId>/` history is migrated
+    automatically (see the `runs migrate` entry).
+  - The viewer's watcher polls only LIVE runs; finished history never touches
+    it. Discovery watches the current day's directory with native `fs.watch`
+    and re-attaches at UTC midnight.
+  - A JSONL index per day and per scenario backs the history list. It is fully
+    rebuildable — rebuilt on start, non-blocking — so a corrupted or missing
+    index degrades the listing, never the runs themselves.
+  - `@unotest/protocol`: new `run-shard` and `run-index` modules (shard path
+    derivation, index record shapes) exported from the root entry.
+
+- Upgrading moves existing run history to the new layout by itself, and
+  Playwright moves to 1.62.
+
+  - The flat `.runs/<runId>/` history is migrated on the first run of the new
+    version. Default is to remove old runs (nobody asked to keep them);
+    `UNOTEST_RUNS_LEGACY=keep` re-files them into date shards instead. The
+    completion marker is written last, so an interrupted or failed move is
+    retried on the next start rather than silently marked done.
+  - New command `unotest-web runs migrate [--dry-run]` — the same migration,
+    runnable FIRST, with a report-only mode. A migration nobody can look at
+    before it happens is one that runs unannounced on someone else's machine.
+  - `playwright` moves to `^1.62.0` in `@unotest/web` and `@unotest/viewer`.
+    Run `npx playwright install` once after upgrading if your browser cache
+    predates it.
+  - Frame capture is now format-parameterised internally, still PNG. WebP was
+    measured and rejected: Chromium's lossless `type: "webp"` is pixel-exact
+    but 1.5× LARGER than PNG on real frames (3.17 MB vs 2.04 MB on one suite).
+  - Fix: the viewer served step screenshots as 403 after the layout change —
+    its asset allow-list still expected the flat layout. The route now has
+    tests.
+
+- The viewer's sidebar becomes a chronological history instead of a flat list.
+
+  - Runs are grouped by the reader's calendar day; a run with a `parentRunId`
+    collapses into its collection's row, and neighbouring identical outcomes
+    collapse run-length style, so a long history stays readable.
+  - Each test carries a chip with its recent trend, and a badge counts tests
+    whose LAST run failed. The badge reads `_latest.json`, so it is correct
+    regardless of how much history the sidebar has loaded; the "Failing now"
+    section matches it by construction.
+  - Fix: `/api/runs` returned a page while the client still expected an array,
+    and the sidebar history rendered empty. The response shape now lives in
+    one place (`shared/runs-page.ts`) and `RunsStore` has tests.
+
+- Overview dashboard — the viewer opens on the health of the whole project
+  instead of "pick something from the sidebar".
+
+  - One tile per scenario, filled by the status of its last run. Tile size is
+    computed from the window, so the entire suite fits without scrolling.
+  - Hovering a tile shows a card with the scenario name, when it last ran, how
+    long it took, and a strip of its recent outcomes. Clicking opens the
+    scenario in a tab. The counters across the top double as filters.
+  - The card's data comes from the run index, not from a request per tile: a
+    field of 200 tests used to mean 200 requests during one sweep of the mouse.
+  - Fix: the status shown next to a scenario in the tree came from whatever
+    slice of history happened to be loaded, instead of the per-scenario index —
+    so it changed as you scrolled.
+
+- Tree rows in the history sidebar share one grid: a collection, a test run and
+  the "open collection run" row now line up on the same vertical and have the
+  same height, and nesting is one indent step per level.
+
 ## [0.18.0] - 2026-08-23
 
 ### Minor Changes