The tests are just awful
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 732
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
The tests have obviously been the readheaded stepchild of the project, and it's gotten to the point that updating the tests to match changes in the core of splinter is now a major bottleneck to progress.
The main problem is that there's tons of repeated code or code with slight variations. If someone would tackle refactoring and cleaning up the tests, it would be a huge service to the rest of 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
The issue does not name any test files, entry points, or specific duplicated code to inspect. Start by surveying the test suite and identifying repeated patterns and variations; done would mean a coordinated cleanup that reduces duplication and keeps tests aligned with core changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- databases, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100