Enabling checkstyle for test and integration test folders #3631
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.
…and adds a check to prohibit the @ignore annotation
Motivation and Context
Using the
@Ignore
annotation in the code base mostly leads to stale code that we don't resolve. It's also led to bugs in a couple of instances. By adding a checkstyle rule to stop coders from using@Ignore
, the intent is to create a mechanism through which we resolve ambiguous issues promptly by removing tests or taking other actions when testing.Modifications
@Ignore
annotationsCHECKSTYLE: OFF
@Ignore
annotation in previous PRs:Testing
Tested locally.
Finding annotations
Example test run: Adding one @ignore annotation at class level and and one at test method level for two tests in the
auth
module, one in the integration test folderit
and one in the standard test foldertest
.Running checks on the whole repo
Running just checkstyle, locally, takes 25s.
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License