-
Notifications
You must be signed in to change notification settings - Fork 554
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
Failing tests can cause coverage drop when refusing coverage drop #624
Comments
thomas07vt
added a commit
to thomas07vt/simplecov
that referenced
this issue
Oct 1, 2017
thomas07vt
added a commit
to thomas07vt/simplecov
that referenced
this issue
Oct 5, 2017
thomas07vt
added a commit
to thomas07vt/simplecov
that referenced
this issue
Oct 5, 2017
thomas07vt
added a commit
to thomas07vt/simplecov
that referenced
this issue
Oct 5, 2017
thomas07vt
added a commit
to thomas07vt/simplecov
that referenced
this issue
Oct 5, 2017
PragTob
added a commit
that referenced
this issue
Oct 6, 2017
…op_on_failed_test Fixes #624 Checks max_coverage_drop on failed tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently simplecov only checks
maximum_coverage_drop
on a successful test run, so a failing test run can write to.last_run.json
with a lower coverage percenage than before.Here is a scenario:
test coverage is at 100%
configure simplecov to refuse coverage drop, or set max coverage drop to 0
run specs
.last_run.json
shows 100%write some new code
write a spec that only partially covers the new code that fails
run specs
.last_run.json
now shows < 100%fix spec to pass, but test coverage still less that 100%
run specs
.last_run.json
still shows < 100%I have PR that I will raise shortly that fixes this
The text was updated successfully, but these errors were encountered: