livepeer / livepeer/go-livepeer-basicnet
Stub out network calls in unit tests
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
A lot of our unit tests here are actually integration tests. This might be an incremental effort, but we should stub out the underlining, libp2p layer in the tests to remove external dependencies. This is causing some inconsistent test behaviors.
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
Start by inventorying the unit tests and locating where the underlying libp2p layer is used. Run the existing test suite to identify inconsistent behavior and external dependencies. Done means the relevant tests stub libp2p calls and run consistently without external network dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100