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

Add developer testing guidelines #70

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

Add developer guidance for writing and running tests, especially around mocked API calls, profile/permission failures, and no-secret regression expectations.

Acceptance criteria

  • Documents standard test commands.
  • Documents how to add MCP tool tests.
  • Documents how to mock api_request safely.
  • Documents expectations for profile/allowed operation tests.
  • Documents no-secret/no-token test expectations.
  • Documents when to add unit vs integration tests.
  • Includes examples or references to existing tests.
Add developer guidance for writing and running tests, especially around mocked API calls, profile/permission failures, and no-secret regression expectations. ## Acceptance criteria * Documents standard test commands. * Documents how to add MCP tool tests. * Documents how to mock `api_request` safely. * Documents expectations for profile/allowed operation tests. * Documents no-secret/no-token test expectations. * Documents when to add unit vs integration tests. * Includes examples or references to existing tests.
jcwalker3 added the documentationtesting labels 2026-07-02 05:44:11 -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 documentation 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#70
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?