Add integration tests for Spike PR→Discord bridge #10

Merged
probablycorey merged 1 commits from probablycorey/test-other-user-pr into main 2026-03-10 16:25:03 +00:00

Summary

  • Move webhook tests from src/gitea/test/ to root tests/ dir, co-locate unit tests with source
  • Add bridge integration test verifying Spike PRs create Discord threads
  • Make Discord client login explicit via startDiscord() instead of side effects on import
  • Setup webhook infra once via preload, tear down on process exit (no more flaky races)
  • Update dev config with new Discord channel and Spike username mapping

Test plan

  • bun test:unit — unit tests
  • bun test:integration — webhook + bridge tests (requires Tailscale + env vars)
  • bun test — both

🤖 Generated with Claude Code

## Summary - Move webhook tests from `src/gitea/test/` to root `tests/` dir, co-locate unit tests with source - Add bridge integration test verifying Spike PRs create Discord threads - Make Discord client login explicit via `startDiscord()` instead of side effects on import - Setup webhook infra once via preload, tear down on process exit (no more flaky races) - Update dev config with new Discord channel and Spike username mapping ## Test plan - `bun test:unit` — unit tests - `bun test:integration` — webhook + bridge tests (requires Tailscale + env vars) - `bun test` — both 🤖 Generated with Claude Code
probablycorey added 1 commit 2026-03-10 16:24:27 +00:00
Add integration tests for Spike PR→Discord bridge
Some checks failed
CI / test (pull_request) Has been cancelled
6b30715fa1
Move webhook tests to root tests/ dir and restructure to be non-flaky. Setup webhook capture server once via preload, tear down on process exit. Tests now clean up their own PRs in afterEach. Added bridge test to verify Spike PRs create Discord threads. Made Discord client login explicit via startDiscord(). Updated config with new dev Discord channel and Spike username mappings.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
probablycorey merged commit abdb81572b into main 2026-03-10 16:25:03 +00:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: probablycorey/workshop#10
No description provided.