Render view tests on the app's own route tree #417

New issue

Closed

opened 2026-10-15 12:34:09 +00:00 by root · 5 comments

root commented

2026-10-15 12:34:09 +00:00

(Migrated from gitlab.core-project.space)

Parent

#408

What to build

View tests render the app's own route tree with a memory history, so each test exercises the loader and search validation that ship. The routes the auth, games and home tests build by hand go; each vertical keeps its MSW worker and fake server.

Seam: S3 — the view tests rendered on the app's route tree.

Acceptance criteria

The auth, games and home tests mount the app's router, not a hand-built route tree.
No test re-declares a loader or a search validator that lives in routes/.
The shared hand-built route helper is deleted once unused.
Every test asserts what it asserted before; only how it mounts changes.
The gate is green.

## Parent #408 ## What to build View tests render the app's own route tree with a memory history, so each test exercises the loader and search validation that ship. The routes the auth, games and home tests build by hand go; each vertical keeps its MSW worker and fake server. Seam: S3 — the view tests rendered on the app's route tree. ## Acceptance criteria - [ ] The auth, games and home tests mount the app's router, not a hand-built route tree. - [ ] No test re-declares a loader or a search validator that lives in `routes/`. - [ ] The shared hand-built route helper is deleted once unused. - [ ] Every test asserts what it asserted before; only how it mounts changes. - [ ] The gate is green.

root commented

2026-10-15 12:34:09 +00:00

(Migrated from gitlab.core-project.space)

marked this issue as related to #408