Issue #13109: Kill mutation for NestedTryDepthCheck#13238
Merged
romani merged 1 commit intocheckstyle:masterfrom Jun 24, 2023
Merged
Issue #13109: Kill mutation for NestedTryDepthCheck#13238romani merged 1 commit intocheckstyle:masterfrom
romani merged 1 commit intocheckstyle:masterfrom
Conversation
1a526e5 to
dac5a8c
Compare
Contributor
Author
|
Github, generate report |
Contributor
Contributor
Author
|
Github, generate report |
Contributor
dac5a8c to
f29a6d3
Compare
f29a6d3 to
6b61797
Compare
40 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #13109: Kill mutation for NestedTryDepthCheck
Check :-
https://checkstyle.org/config_coding.html#NestedTryDepth
Mutation
checkstyle/config/pitest-suppressions/pitest-coding-2-suppressions.xml
Lines 111 to 118 in 3f25c37
Explaination
All the values will increase by visit token and decrement by leave Token so I don't see we should require to reset the value using beginTree because at the end it will be reset by leaveToken
but lets see Regression
Regression
Report-1 :- https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/dac5a8c_2023201111/reports/diff/index.html
Report-2 :- https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/dac5a8c_2023225538/reports/diff/index.html
Diff Regression config: https://gist.githubusercontent.com/Kevin222004/1a5e00ff61776c73c881b8752b0495a0/raw/77a12ab981e96fabfcd4b674d3f8d825df3ea946/NestedTry.xml
Diff Regression projects: https://gist.githubusercontent.com/Kevin222004/21e3934e85f802e2fbd48af06d122364/raw/604256badd733d8568064f371d55657c04b00dfd/test-projects-2.properties
Report label: R2