Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve test coverage to >85% and make it a blocker for PRs #233

Closed
robskillington opened this issue Jan 25, 2017 · 0 comments
Closed

Improve test coverage to >85% and make it a blocker for PRs #233

robskillington opened this issue Jan 25, 2017 · 0 comments
Labels
area:db All issues pertaining to dbnode

Comments

@robskillington
Copy link
Collaborator

robskillington commented Jan 25, 2017 •
edited

Need to set the coveralls thresholds at coveralls.io once achieved >85%.
@robskillington robskillington changed the title Improve test coverage to >85% Improve test coverage to >85% and make it a blocker for PRs Jan 25, 2017
@prateek prateek added the area:db All issues pertaining to dbnode label May 12, 2018
cw9 pushed a commit that referenced this issue Oct 14, 2018
@schallert
[client] Allow configuration of watch w/ revision (#233)
b243df8 
This allows `WatchWithRevision` to be set on a per-client basis.
cw9 pushed a commit that referenced this issue Oct 16, 2018
@schallert
[client] Allow configuration of watch w/ revision (#233)
c07261e 
This allows `WatchWithRevision` to be set on a per-client basis.
cw9 pushed a commit that referenced this issue Oct 16, 2018
@schallert
[client] Allow configuration of watch w/ revision (#233)
a401ce7 
This allows `WatchWithRevision` to be set on a per-client basis.
cw9 pushed a commit that referenced this issue Oct 16, 2018
@schallert @cw9
[client] Allow configuration of watch w/ revision (#233)
332114f 
This allows `WatchWithRevision` to be set on a per-client basis.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:db All issues pertaining to dbnode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prateek @robskillington @gibbscullen