Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Add Docker-based Gitea integration test suite #66

New Issue
Open
opened 2026-07-02 05:43:21 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:43:21 -05:00
Owner
Copy Link
Copy Source

Current tests rely heavily on mocked api_request responses. That is valuable for unit testing, but it does not prove compatibility with real Gitea API behavior around pagination, permissions, label endpoints, PR review endpoints, and error payloads.

Add an optional Docker-based integration test suite against a local/containerized Gitea instance.

Acceptance criteria

  • Integration test harness can start or connect to a local test Gitea instance.
  • Tests are optional and skipped unless explicitly enabled.
  • Covers issue listing and pagination.
  • Covers PR listing and pagination.
  • Covers label add/remove behavior.
  • Covers permission denial/fail-closed behavior.
  • Covers review/comment/merge eligibility paths where feasible.
  • Does not require production credentials.
  • Does not leak tokens in logs.
  • Unit tests remain fast and unchanged by default.
Current tests rely heavily on mocked `api_request` responses. That is valuable for unit testing, but it does not prove compatibility with real Gitea API behavior around pagination, permissions, label endpoints, PR review endpoints, and error payloads. Add an optional Docker-based integration test suite against a local/containerized Gitea instance. ## Acceptance criteria * Integration test harness can start or connect to a local test Gitea instance. * Tests are optional and skipped unless explicitly enabled. * Covers issue listing and pagination. * Covers PR listing and pagination. * Covers label add/remove behavior. * Covers permission denial/fail-closed behavior. * Covers review/comment/merge eligibility paths where feasible. * Does not require production credentials. * Does not leak tokens in logs. * Unit tests remain fast and unchanged by default.
jcwalker3 added the importanttestingintegration labels 2026-07-02 05:43:56 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label important integration testing
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#66
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?