lbryio / lbryio/wallet-sync-server
Integration tests for unhappy paths
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Right now I have pretty good unit test coverage and a couple happy paths for integration tests. Maybe we could stand to have a few unhappy paths for integration.
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
No files or specific integration scenarios are named. Start by locating the existing integration tests and their happy-path cases, then identify representative failure paths; done means those unhappy paths are covered and the integration test suite passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100