-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Testing conventions now checks for tests in main #37321
Conversation
This is the last outstanding feature of the old NamingConventionsTask, so time to remove it.
Pinging @elastic/es-core-infra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
// some test projects don't have a main source set | ||
return Collections.emptySet(); | ||
} | ||
return Boilerplate.getJavaSourceSets(getProject()).getByName(SourceSet.MAIN_SOURCE_SET_NAME) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need to re-get the source set, you already have it above to use?
checkNoneExists( | ||
"Classes matching the test naming convention should be in test not main", | ||
getMainClassNames().stream() | ||
.filter(this::implementsNamingConvention) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this could be moved to the input property getter
* Testing conventions now checks for tests in main This is the last outstanding feature of the old NamingConventionsTask, so time to remove it. * PR review
This is the last outstanding feature of the old
NamingConventionsTask
, so time to remove it.