-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Resolve Pitest Issues - JavadocMethodCheck (4) #7925
Comments
I am on it |
@rnveach For this issue the line is I have hardcoded the mutation in a new branch and uploaded the branch to my forked checkstyle repo. HardCoded Mutation - hembhagat99@50299fd Pitest-Regression Report: Here, mutation deals with Param Tags. So, I have used default configuration as the default value of I have run the regression on three projects.
So far no changes are detected. |
…Mutation Hardcoded
@rnveach Here is the full code of function which uses this condition, private void processTypeParams(DetailAST ast) {
final DetailAST params =
ast.findFirstToken(TokenTypes.TYPE_PARAMETERS);
final Map<String, ClassInfo> paramsMap = new HashMap<>();
currentTypeParams.push(paramsMap);
if (params != null) {
for (DetailAST child = params.getFirstChild();
child != null;
child = child.getNextSibling()) {
if (child.getType() != TokenTypes.TYPE_PARAMETER) {
final DetailAST bounds =
child.findFirstToken(TokenTypes.TYPE_UPPER_BOUNDS);
if (bounds != null) {
final FullIdent name =
FullIdent.createFullIdentBelow(bounds);
final ClassInfo classInfo =
createClassInfo(new Token(name), currentClassName);
final String alias =
child.findFirstToken(TokenTypes.IDENT).getText();
paramsMap.put(alias, classInfo);
}
}
}
}
}
So, our condition checks whether the child is of type The next statement is, final DetailAST bounds =
child.findFirstToken(TokenTypes.TYPE_UPPER_BOUNDS);
if (bounds != null) { It gets the So, we don't need the previous condition. |
…Mutation Hardcoded
fixed in scope of #7980 |
Child issue of #7797 ,
checkstyle/.ci/pitest.sh
Line 185 in f9131f9
The text was updated successfully, but these errors were encountered: