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

New issue

Open

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

hexajon commented

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

Owner

What to build

A test that fails when a test file starts a fake HTTP server for a forge, or replaces the forge client with a fake. The failure names the file and the line.

Acceptance

The current tree passes.
A new fake forge server or fake forge client in any test fails the gate, with its file and line.

Needs #679, #680, #681, and #682. Part of #674.

## What to build A test that fails when a test file starts a fake HTTP server for a forge, or replaces the forge client with a fake. The failure names the file and the line. ## Acceptance - The current tree passes. - A new fake forge server or fake forge client in any test fails the gate, with its file and line. Needs #679, #680, #681, and #682. Part of #674.

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:11 +00:00

#679 tests: move the internal/gitea tests from fake forges to the harness

hexajon added a new dependency

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

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