cayleygraph/cayley

Improve Integration Tests using `.Save()` and `.Or()`

Open

#238 opened on Apr 21, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (14,291 stars) (1,277 forks)batch import
Test Coveragegood first issue

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

Tech stack
go
Domain
databasetesting
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go basicsUnderstanding of graph iteratorsFamiliarity with gocov
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue asks to add integration tests for the Optional and Or iterators in cayley test.go. Start by examining the existing test structure and the gocov coverage report to identify uncovered code. Then write queries that exercise these iterators, aiming to raise coverage from 53.45%. Use `gocov test coverpkg=./graph/iterator .` to measure improvements.