sixfold-space/madtea
sixfold-space/madtea
SHA256
2
0
Fork 0
Code Issues 221 Pull requests Projects Releases 13 Packages Wiki Activity Actions 9

feat(testforge): #677 throwaway-forge test harness, tested at baseline and latest #729

Merged
hexajon merged 2 commits from issue-677-forge-test-harness-matrix into main 2026-10-06 16:52:30 +00:00
Conversation 0 Commits 2 Files changed 31 +3552 -3
hexajon commented 2026-10-06 16:52:28 +00:00
Owner
Copy link

Summary

Add the forge-test harness (ADR 0052): it downloads pinned, checksum-verified Forgejo, Gitea and Traefik binaries, starts a throwaway forge behind a rate-limited Traefik proxy as a non-root user, and gives a test a client to talk to it through the proxy.

Each forge is pinned at two versions and every forge test runs against both: a fixed baseline (Forgejo 15.0.1, Gitea 1.26.1, the versions the compatibility specs and the gap list target) and the latest release. The baseline version is authored in forge-pins.json; the forge-pins bump command fills every checksum and tracks the latest, so no version is hand-edited or hardcoded.

Acceptance, all verified against the real throwaway servers: a client reads each forge's version through the proxy; a fast request stream gets the proxy's rate-limit refusal; a stopped forge surfaces a client error; an unchecked binary fails the run and names the file; the bump writes the pin file and a second run with no new release changes nothing.

Refs #677

## Summary Add the forge-test harness (ADR 0052): it downloads pinned, checksum-verified Forgejo, Gitea and Traefik binaries, starts a throwaway forge behind a rate-limited Traefik proxy as a non-root user, and gives a test a client to talk to it through the proxy. Each forge is pinned at two versions and every forge test runs against both: a fixed baseline (Forgejo 15.0.1, Gitea 1.26.1, the versions the compatibility specs and the gap list target) and the latest release. The baseline version is authored in forge-pins.json; the forge-pins bump command fills every checksum and tracks the latest, so no version is hand-edited or hardcoded. Acceptance, all verified against the real throwaway servers: a client reads each forge's version through the proxy; a fast request stream gets the proxy's rate-limit refusal; a stopped forge surfaces a client error; an unchecked binary fails the run and names the file; the bump writes the pin file and a second run with no new release changes nothing. Refs #677 
Initial internal/testforge harness and the madtea-dev forge-pins command:
pinned forge binaries with checksum verification and a checksum-keyed cache,
free-port selection, a Traefik reverse-proxy front, Forgejo and Gitea starters,
acceptance tests behind the forge build tag, and the pin-bump command. Incomplete
and not yet compiling; committed to preserve the work. Refs #677.
feat(testforge): #677 test each forge at a baseline and latest version
All checks were successful
ci / mcp-conformance (pull_request) Successful in 1m32s
Details
drift / govulncheck (pull_request) Has been skipped
Details
drift / forgejo-smoke (pull_request) Has been skipped
Details
drift / surface-diff (pull_request) Successful in 40s
Details
ci / mcp-conformance (push) Successful in -18s
Details
drift / govulncheck (push) Has been skipped
Details
drift / surface-diff (push) Successful in -24s
Details
drift / forgejo-smoke (push) Has been skipped
Details
ci / gate (push) Successful in 9m42s
Details
ci / gate (pull_request) Successful in 18m57s
Details
4c28163967
 
Grow the pin schema to a baseline+latest pair per forge, with the baseline
version authored in forge-pins.json and the bump filling both checksums. The
harness and its acceptance tests run against both, so the compat-stamped
baseline (Forgejo 15.0.1, Gitea 1.26.1) stays under test while the latest
major is also exercised. Traefik stays a single pin. Record the matrix in
ADR 0052.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
breaking
Breaking change - flag for release notes

  
bug
Something is not working

  
documentation
Documentation only

  
enhancement
New feature

  
epic
Tracking epic with dependency children

  
good first issue
Interested in contributing? Get started here.

  
help wanted
Maintainer would welcome outside help

  
refactoring
Code restructuring without behavior changes

  
resolution/duplicate
Closed as duplicate of another issue

  
resolution/invalid
Closed as invalid or not reproducible

  
resolution/wontfix
Closed as won't fix

  
security
Security issue or hardening

  
severity/critical
Security severity: critical

  
severity/high
Security severity: high

  
severity/low
Security severity: low

  
severity/medium
Security severity: medium

  
status/abandoned
Someone started, then walked away - up for grabs

  
status/blocked
Blocked by another issue or an external dependency

  
status/needs-decision
Waiting on a maintainer decision; workable once decided

  
status/needs-info
Waiting on reporter / more information before work can start

  
status/needs-verification
Done except verification in a live interactive session

  
testing
Test suite / CI infrastructure work

  
upstream
Related to an upstream repository, already reported there

No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
sixfold-space/madtea!729
No description provided.