sixfold-space/madtea

SHA256

Fork 0

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

New issue

Open

opened 2026-09-29 19:28:46 +00:00 by hexajon · 0 comments

hexajon commented

2026-09-29 19:28:46 +00:00

Owner

Today:

230 uses of a fake HTTP server in 86 test files stand in for the forge.
The forgejo-smoke job in .forgejo/workflows/drift.yml starts a real Forgejo, but its admin bootstrap needs docker exec, so it runs only where RUN_FORGEJO_SMOKE is set and is skipped elsewhere. It covers Forgejo only.

Scope:

A harness that starts a throwaway Forgejo and a throwaway Gitea from pinned binaries with checked checksums, each behind a pinned reverse proxy with a rate limit. Each forge's own CLI creates a fresh admin and a token. No docker, and no secret.
Tooling bumps the version pins, never a hand edit.
Every forge test moves onto the harness. A fault comes from the real servers: a large fixture, a stopped forge, a renamed repo, or the proxy's rate limit.
The docker-exec bootstrap of forgejo-smoke goes, and its commands run on the harness against both forges.
The gate and CI run the same tests, and none is skipped.

Acceptance:

No test starts a fake HTTP server for a forge, and no test replaces the forge client with a fake.
The gate and CI each run the forge tests against both forges, and report no skipped forge test.

Decision record: ADR 0017.

Children

The work runs in these children, in the order it can run:

#677 the harness and the pin tool.
#678 the gate and CI run the forge tests, and the docker-exec smoke job goes. Needs #677.
#679 internal/gitea. Needs #677.
#680 internal/mcp. Needs #677.
#681 internal/service. Needs #677.
#682 every other package. Needs #677.
#683 the gate fails when a test fakes a forge. Needs #679, #680, #681, and #682.

Done when every child is closed.

ADR 0017 says that a test of what a forge returns or accepts runs against throwaway Forgejo and Gitea servers that the test run starts, behind a real reverse proxy. The tests run the same way in the local gate and in CI, none is skipped, and no test uses a fake server or a fake forge client. Today: - 230 uses of a fake HTTP server in 86 test files stand in for the forge. - The `forgejo-smoke` job in `.forgejo/workflows/drift.yml` starts a real Forgejo, but its admin bootstrap needs `docker exec`, so it runs only where `RUN_FORGEJO_SMOKE` is set and is skipped elsewhere. It covers Forgejo only. Scope: - A harness that starts a throwaway Forgejo and a throwaway Gitea from pinned binaries with checked checksums, each behind a pinned reverse proxy with a rate limit. Each forge's own CLI creates a fresh admin and a token. No docker, and no secret. - Tooling bumps the version pins, never a hand edit. - Every forge test moves onto the harness. A fault comes from the real servers: a large fixture, a stopped forge, a renamed repo, or the proxy's rate limit. - The docker-exec bootstrap of `forgejo-smoke` goes, and its commands run on the harness against both forges. - The gate and CI run the same tests, and none is skipped. Acceptance: - No test starts a fake HTTP server for a forge, and no test replaces the forge client with a fake. - The gate and CI each run the forge tests against both forges, and report no skipped forge test. Decision record: ADR 0017. ## Children The work runs in these children, in the order it can run: - #677 the harness and the pin tool. - #678 the gate and CI run the forge tests, and the docker-exec smoke job goes. Needs #677. - #679 `internal/gitea`. Needs #677. - #680 `internal/mcp`. Needs #677. - #681 `internal/service`. Needs #677. - #682 every other package. Needs #677. - #683 the gate fails when a test fakes a forge. Needs #679, #680, #681, and #682. Done when every child is closed.

hexajon referenced this issue

2026-09-29 19:31:31 +00:00

epic: v0.20.0 - breaking: clearer ADR tooling and the write guard on every surface #675

hexajon added a new dependency

2026-09-29 19:32:18 +00:00

#675 epic: v0.20.0 - breaking: clearer ADR tooling and the write guard on every surface

hexajon added a new dependency

2026-09-29 19:36:02 +00:00

#530 adr check: resolve cross-repo record links, so an impacts pair cannot go one-way or dangle

hexajon added a new dependency

2026-09-29 19:36:03 +00:00

#632 adr check: C11 drops the host from an issue URL and reads the link on the record's own forge

hexajon added a new dependency

2026-09-29 19:36:03 +00:00

#658 adr check: verify every file reference in a record

hexajon added a new dependency

2026-09-29 19:36:03 +00:00

#655 adr check: find the author of a status change as the forge PR author

hexajon added a new dependency

2026-09-29 19:36:04 +00:00

#656 adr check: count contributors by access to the repo

hexajon added a new dependency

2026-09-29 19:36:04 +00:00

#661 adr check: enforce sign-off on decided records

hexajon added a new dependency

2026-09-29 19:36:04 +00:00

#665 guard: refuse every commit on the default branch after the first push, with no override

hexajon added a new dependency

2026-09-29 19:36:05 +00:00

#666 guard: prove every removal with the forge's answer, not local state

hexajon added a new dependency

2026-09-29 19:36:05 +00:00

#668 guard: the raw API passthrough keeps every limit

hexajon added a new dependency

2026-09-29 19:36:06 +00:00

#671 adr check: a decided record with no decision issue fails sign-off, except the init record

hexajon added a new dependency

2026-09-29 19:36:06 +00:00

#672 adr check: later status changes and edits to a decided record need sign-off

hexajon referenced this issue

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

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

hexajon referenced this issue

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

ci: run the forge tests on the harness in the gate and in CI, and remove the docker-exec smoke job #678

hexajon referenced this issue

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

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

hexajon referenced this issue

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

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

hexajon referenced this issue

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

tests: move the internal/service tests from fake forges to the harness #681

hexajon referenced this issue

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

tests: move the remaining tests from fake forges to the harness #682

hexajon referenced this issue

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

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

hexajon changed title from ~~tests: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy~~ to epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy

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

hexajon added a new dependency

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

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

hexajon added a new dependency

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

#678 ci: run the forge tests on the harness in the gate and in CI, and remove the docker-exec smoke job

hexajon added a new dependency

2026-09-29 23:06:10 +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:10 +00:00