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

Issue #4394: increase coverage of pitest-checkstyle-api profile to 100% #4740

Merged
merged 1 commit into from Jul 17, 2017

Conversation

Nimfadora
Copy link
Contributor

Issue #4394

pitest-checkstyle-api profile before changes

increased mutation threshold for pitest-checkstyle-api profile by 4%
current threshold: 100%
execution time: 3:31 min

one mutation left: I have no idea how to test it

@romani
Copy link
Member

romani commented Jul 17, 2017

one mutation left: I have no idea how to test it

remove this line , it is useless code as buf is temporal variable.
it is sad that pitest still allow you to set 100 as threshhold , I filed an issue on pitest - hcoles/pitest#375

@codecov-io
Copy link

codecov-io commented Jul 17, 2017

Codecov Report

Merging #4740 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #4740   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files         287     287           
  Lines       15388   15388           
  Branches     3501    3501           
======================================
  Hits        15388   15388

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 475ec10...0c3e25e. Read the comment docs.

@romani romani merged commit b06e11c into checkstyle:master Jul 17, 2017
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

3 participants