Server/code coverage の導入
Open
Nobody has claimed this yet.
server
- Dominant language
- Go
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
testを書いてから
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue only asks for server code coverage and says to write tests first; it names no files, entry points, or existing tests. Start by locating the server implementation and test suite, then determine how coverage should be measured. Done should mean the server has tests and a repeatable coverage result, but the target coverage and tooling are unspecified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100