Klaus/gitea-mcp
1
0
Fork 0
Code Issues 12 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

stability: fill test coverage gaps in write-heavy modules #7

New Issue
Open
opened 2026-05-23 18:30:35 +00:00 by Klaus · 0 comments
Klaus commented 2026-05-23 18:30:35 +00:00
Owner
Copy Link
Copy Source

Problem

Test files exist for pull, issue, milestone, packages, search, wiki, repo (slim/tree), pkg/params, pkg/gitea (rest/redirect), pkg/slim, and operation top-level. But several write-heavy modules have no test file at all:

  • operation/user/
  • operation/label/
  • operation/timetracking/
  • operation/notification/
  • operation/actions/ (only logs_test.go — runs.go and config.go untested)
  • operation/repo/ write paths (branch.go, tag.go, file.go, release.go, commit.go, repo.go)

These are exactly the surfaces where a silent regression (wrong field name, broken pagination, missing required param) is most expensive.

Suggested direction

Add table-driven tests with an httptest.Server standing in for Gitea. One test per public tool method covering: happy path, missing required param, propagated SDK error. The operation/pull/pull_test.go pattern is a fine starting template.

## Problem Test files exist for `pull`, `issue`, `milestone`, `packages`, `search`, `wiki`, `repo (slim/tree)`, `pkg/params`, `pkg/gitea (rest/redirect)`, `pkg/slim`, and `operation` top-level. But several write-heavy modules have **no** test file at all: - `operation/user/` - `operation/label/` - `operation/timetracking/` - `operation/notification/` - `operation/actions/` (only `logs_test.go` — `runs.go` and `config.go` untested) - `operation/repo/` write paths (`branch.go`, `tag.go`, `file.go`, `release.go`, `commit.go`, `repo.go`) These are exactly the surfaces where a silent regression (wrong field name, broken pagination, missing required param) is most expensive. ## Suggested direction Add table-driven tests with an `httptest.Server` standing in for Gitea. One test per public tool method covering: happy path, missing required param, propagated SDK error. The `operation/pull/pull_test.go` pattern is a fine starting template.
Klaus referenced this issue from a commit 2026-05-23 18:47:28 +00:00
fix bug (#7)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Klaus
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Klaus/gitea-mcp#7
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?