Don't exclude the naming rules by default for tests #4438
Merged
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.
In general, the rules that apply to good naming patterns in production code can be applied for the test code too. The only exception are the function names. And to be honest that's mainly because of JUnit but I don't want to cross that bridge yet. So this PR remove the excludes for all the rules except
FunctionNaming
.I also changed our (not the default one) value for
TopLevelPropertyNaming.constantPattern:
. Otherwise I would need to do this changes like this that I think that are way worst:closes #4144