test: enforce shared SQL fixtures

[sentry-junior]

Use one shared SQL fixture boundary for Junior tests.

• Normal database tests use createJuniorSqlFixture, which opens a rollback-only transaction against the migrated per-worker Postgres database.
• Migration contract tests use an explicit empty fixture through the same shared module.
• The test architecture check rejects direct Postgres fixture imports, the ambiguous old local fixture, and empty fixtures outside the approved migration contract tests.
• Integration CI allows 20 seconds for shared-runner variance.

Evidence:

• The release branch failed three times with different timed-out tests.
• slack-schedule-tools.test.ts took 54.9–107.5 seconds and created a new database plus applied 43 migrations for each of 52 tests.
• With the migrated transaction fixture, three local runs passed all 52 tests in 33.9–44.2 seconds.

Checks:

• pnpm test-architecture:check
• pnpm --filter @sentry/junior typecheck
• pnpm --filter @sentry/junior exec vitest run --maxWorkers=2 --testTimeout=20000 tests/integration/slack-schedule-tools.test.ts
• pnpm --filter @sentry/junior exec vitest run tests/component/artifacts.test.ts tests/component/conversation-message-search.test.ts
• pnpm --filter @sentry/junior exec vitest run --testTimeout=20000 tests/integration/workspace-snapshot-migration.test.ts

via David Cramer.

--

View Junior Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
junior-docs	Ready	Preview	Sep 17, 2026 8:57pm UTC

[github-actions]

1 screenshot change — 1 changed · 0 added · 0 removed

Review screenshots in Frameshift

Automation Executions · Desktop Changed