cayleygraph / cayleygraph/cayley
Improve Integration Tests using `.Save()` and `.Or()`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 15.1k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
gocov test -coverpkg=./graph/iterator . | gocov report shows we cover the base iterators in our integration test with a code coverage of 53.45% (as of this writing). Most of these come from lack of testing the Optional iterator or the Or iterator.
Simple enough: add some (hopefully grunty) integration/benchmark queries to cayley_test.go and raise this number considerably.
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 with cayley_test.go and review the existing integration and benchmark queries. Run the gocov command from the issue to establish the current coverage, then add queries that exercise the Optional and Or iterators. Done means the integration coverage is substantially higher than 53.45%.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100