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.

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

Lower coverage thresholds for system tests. #79

Merged
merged 1 commit into from Mar 10, 2016

Conversation

mstemm
Copy link

@mstemm mstemm commented Mar 10, 2016

The only lines not covered are not specifying a port at all when
running juttle-engine (which doesn't match our use of getFreePort) and
daemonizing, which we don't want to handle.

@rlgomes

The only lines not covered are not specifying a port at all when
running juttle-engine (which doesn't match our use of getFreePort) and
daemonizing, which we don't want to handle.
@rlgomes
Copy link
Contributor

rlgomes commented Mar 10, 2016

#80 so we can bump coverage back up

@rlgomes
Copy link
Contributor

rlgomes commented Mar 10, 2016

+1 the RED on here was due to the examples tests not checking the containres are up and shall be fixed in this PR where I have a nice way of handling the wait: #76

mstemm pushed a commit that referenced this pull request Mar 10, 2016
Lower coverage thresholds for system tests.
@mstemm mstemm merged commit e1209ad into master Mar 10, 2016
@mstemm mstemm deleted the decrease-coverage-thresholds branch March 10, 2016 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants