Skip to content
This repository was archived by the owner on May 11, 2026. It is now read-only.

chore(tests): scope jest test discovery to project test directory#633

Merged
wa0x6e merged 1 commit into
masterfrom
fix/jest-exclude-worktrees
Apr 9, 2026
Merged

chore(tests): scope jest test discovery to project test directory#633
wa0x6e merged 1 commit into
masterfrom
fix/jest-exclude-worktrees

Conversation

@wa0x6e

@wa0x6e wa0x6e commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Jest had no explicit roots configured, so it discovered and ran tests from .claude/worktrees/ alongside the main test/ directory. Both test sets inserted the same fixtures into the shared snapshot_sequencer_test database, causing ER_DUP_ENTRY failures across alias, actions, and ingestor integration tests (14 failures).

Changes

  • ✏️ Added roots: ['<rootDir>/test'] to jest.config.ts to restrict test discovery to the project's own test directory

Test plan

  • Run yarn test:integration and confirm duplicate entry failures are resolved (14 failures → 1 unrelated failure in unfollows.test.ts)

Jest was discovering and running tests from .claude/worktrees/ alongside
the main test/ directory, causing duplicate fixture inserts against the
same test database and ER_DUP_ENTRY failures.
@wa0x6e
wa0x6e requested a review from ChaituVR April 9, 2026 08:24
@wa0x6e wa0x6e changed the title fix: scope jest test discovery to project test directory chore(tests): scope jest test discovery to project test directory Apr 9, 2026

@ChaituVR ChaituVR left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utAck

@wa0x6e
wa0x6e merged commit a18c3f7 into master Apr 9, 2026
2 checks passed
@wa0x6e
wa0x6e deleted the fix/jest-exclude-worktrees branch April 9, 2026 08:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants