Skip to content

chore(rendering): colocate tests, remove the lone __tests__ dir - #482

Merged
Juliusolsson05 merged 1 commit into
integration/rendering-pipelinefrom
chore/colocate-rendering-tests
Jul 7, 2026
Merged

Juliusolsson05 merged 1 commit into
integration/rendering-pipelinefrom
chore/colocate-rendering-tests

Conversation

@Juliusolsson05

Copy link
Copy Markdown
Owner

Workstream 3. rendering/__tests__/ was the only __tests__ dir in the repo; everywhere else colocates. Moved 1:1 tests next to their source (adapter/model/observations/policy/view/shadow/replay) and the cross-cutting corpus + e2e fixture tests to the rendering/ root. Pure move — the src/**/*.test.ts glob already matches colocated files; 170 rendering tests unchanged, full suite 434, gates clean.

🤖 Generated with Claude Code

…stream 3)

src/renderer/src/rendering/__tests__/ was the ONLY __tests__ directory in
the repo — everywhere else colocates test next to source. Standardized on
colocation:

- 1:1 tests moved next to their source: adapter → adapter/
  collectLedgerInput.test.ts; committed/semantic → observations/;
  ledger/ghostPredicate/unknowns → model/; foldPolicy → policy/;
  ledgerFeedItems → view/; shadowDiff → shadow/; replay* → replay/
  (invariants.test.ts, recordedSession.test.ts).
- Cross-cutting tests with no single source (the corpus + e2e fixtures)
  moved to the rendering/ root: bundleCorpus, recordingCorpus,
  shadowParity, fixtures.*.
- bundleCorpus/recordingCorpus fixture paths dropped one ../ (moved up a
  level).

Pure move — vitest's src/**/*.test.ts glob already matches colocated
files. 170 rendering tests unchanged; full unit suite 434; both gates
clean. (Historical research docs keep their point-in-time __tests__
references by design.)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Juliusolsson05
Juliusolsson05 merged commit 69c4366 into integration/rendering-pipeline Jul 7, 2026
@Juliusolsson05
Juliusolsson05 deleted the chore/colocate-rendering-tests branch July 7, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant