You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is some sample code that produces those issues
@SpringBootTestclassEndpointHealthCheckIntegrationTestextendsSpecification {
@AutowiredprivateEndpointHealthCheck healthCheck
def"endpoint is up and running"() {
when: 'health is queried'Health health = healthCheck.health().block()
then: 'status should be up'
health.status ==Status.UP
}
}
I resolve those issues as false positives and have to do it for every test method which is kinda annoying.
the convention for spock test methods is to use def and write a meaningful name (as GString) instead of a JUnit-style identifier
the JUnit rule is applied to this kind of tests (I guess because Spock uses JUnit in the background). It clearly can't identify the method as a test and tells me that all methods but tests should not be public.
The text was updated successfully, but these errors were encountered:
We use the plugin mainly for our tests which are written in the awesome spock framework.
However, we noticed that at least three rules are applied to the test method name that don't make any sense in the context of a test method:
Here is some sample code that produces those issues
I resolve those issues as false positives and have to do it for every test method which is kinda annoying.
def
and write a meaningful name (as GString) instead of a JUnit-style identifierThe text was updated successfully, but these errors were encountered: