mr-onion

Test cases: Test suite (TST)

Section 3.9 of the test plan, which keeps the app overview, the feature status, the known limitations and the index of areas. Since TFP-253 each area’s cases are in a file of their own; a ticket names the area it touches.

ID Test Expected Result Status
TST-01 Unit tests that need a real browser skip, with the reason, where Chromium isn’t installed Ten real-browser unit tests skip, with the reason, without Chromium. Evidence. ✅
TST-02 Real-browser unit tests run Playwright in a folder of their own Every Playwright CLI run in a unit test gets its own folder under .playwright-unit-runs/. Evidence. ✅
TST-03 A unit test that starts a run waits until the run is saved, not just finished waitForSavedRun(runId, limit) returns once the job has its result and its run.json is written (no run.json.tmp left). Evidence. ✅
TST-04 CI runs the unit suite and the template check nightly and on manual dispatch, not on every push Six jobs, on a 02:00 UTC schedule and on workflow_dispatch: audit (TFP-266), dead-code (TFP-259: npx knip, knip.jsonc), issue (TFP-252, TST-07), notify (TFP-217, TST-06) and these two. Evidence. ✅
TST-05 A real-browser case that needs a worker count sets it, so it doesn’t depend on the machine As the ownership stub does, the override stands in for the machine’s limit, in tests only; nothing in the app sets it, and a capped host still gets at most 3. Evidence. ✅
TST-06 Every nightly says how it went, on its own page and by email notify writes the summary to the run’s page and emails it through Gmail to CI_REPORT_TO. Evidence. ✅
TST-07 A red nightly opens or updates one failure issue, and the next green one closes it One “Nightly failing” issue: opened, commented on while red, closed when green; the email links it. Evidence. ✅
TST-08 No old name in living text (npm run check:old-name, in PR Validation) Every “testforge”, in any case, in the repo’s tracked text files is allowed by an entry in scripts/old-name/allowlist.json, and every entry has a reason and allows something; otherwise exit 1, naming each hit or entry. Phase 48 (TFP-280). Measured 2026-11-11: 16,838 hits in 1,175 files (tracked paths included), all allowed by 52 of 52 entries, exit 0. The old name planted in README: exit 1, naming README.md:514; an entry for a file that doesn’t exist: exit 1, “allows nothing”; an entry without its reason: stops, naming the entry. ✅