tests: move the remaining tests from fake forges to the harness #682
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#674 epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy
sixfold-space/madtea
#683 tests: fail the gate when a test fakes a forge
sixfold-space/madtea
Reference
sixfold-space/madtea#682
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What to build
Every test outside
internal/gitea,internal/mcp, andinternal/servicethat starts a fake HTTP server for a forge, or replaces the forge client with a fake, runs against the harness instead, on both forges. Today these tests are ininternal/cmd,internal/config, andinternal/git. 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
internal/gitea,internal/mcp, andinternal/servicestarts a fake HTTP server for a forge or replaces the forge client with a fake.Needs #677. Part of #674.