Question

Our test suite is growing quickly and we have reached a point where our more functional tests are dependent on other systems.

We use gradle test tasks to run these tests using the include and exclude filters but this is becoming cumbersome because we are having to name our tests in a particular way.

Our current approach is to name our tests in the following way:

class AppleSingleServiceTest {}
class BananaMultiServiceTest {}
class KiwiIntegrationTest {}

and then include tests in the relevant task using

include '**/*SingleServiceTest.class'
include '**/*MultiServiceTest.class'
include '**/*IntegrationTest.class'

Is it possible find test classes in gradle by looking at annotations?

@SingleServiceTest
public class AppleTest {}

I think any tests that are not annotated would then be run as normal unit tests, so if you forget to annotate a more functional test it will fail

An example of a single service test is a selenium test where any external dependencies of the SUT are stubbed

An example of a multi service test is one where some but maybe not all external dependencies are not stubbed

Answer 1

The feature you are asking for doesn’t currently exist, but you can make a feature request at http://forums.gradle.org. Or you can use the (cumbersome) JUnit @Category, which requires you to define test suites.