tests: move the internal/mcp tests from fake forges to the harness #680

New issue

Open

opened 2026-09-29 23:05:28 +00:00 by hexajon · 0 comments

hexajon commented

2026-09-29 23:05:28 +00:00

Owner

What to build

Every test in internal/mcp that starts a fake HTTP server for a forge, or replaces the forge client with a fake, runs against the harness instead, on both forges. A fault comes from the real servers: a large fixture, a stopped forge, a renamed repo, or the proxy's rate limit. A fake server for something that is not a forge stays.

Acceptance

No test in internal/mcp starts a fake HTTP server for a forge or replaces the forge client with a fake.
The moved tests run against Forgejo and Gitea, and none is skipped.

Needs #677. Part of #674.

## What to build Every test in `internal/mcp` that starts a fake HTTP server for a forge, or replaces the forge client with a fake, runs against the harness instead, on both forges. A fault comes from the real servers: a large fixture, a stopped forge, a renamed repo, or the proxy's rate limit. A fake server for something that is not a forge stays. ## Acceptance - No test in `internal/mcp` starts a fake HTTP server for a forge or replaces the forge client with a fake. - The moved tests run against Forgejo and Gitea, and none is skipped. Needs #677. Part of #674.

hexajon referenced this issue

2026-09-29 23:05:48 +00:00

tests: fail the gate when a test fakes a forge #683

hexajon referenced this issue

2026-09-29 23:06:02 +00:00

epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy #674

hexajon added a new dependency

2026-09-29 23:06:10 +00:00

#674 epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy

hexajon added a new dependency

2026-09-29 23:06:10 +00:00

#677 tests: add a harness that starts throwaway Forgejo and Gitea servers behind Traefik