Setup mocks to be used for tests
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Problem Statement
In order to support creating tests, especially since we have some fairly complex dependencies, it would be helpful to have a set of mocks ready.
Proposed Solution
Mocks from Holepunch can be used as an example. Leveraging the same test tools across projects would be helpful.
Exit Criteria
- Basic setup for
mockgenestablished for the project
Contributor guide
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
Start by reviewing the Go repository's current test tooling and compare the proposed approach with Holepunch's mock setup. Establish the basic mockgen configuration for this project and verify that it supports generating mocks for tests; no specific file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100