I thought the correct syntax was more like below, where you prefix the target with geode-core, or geode-lucene, etc.
./gradlew geode-core:test -Dtest.single=StringUtilsJUnitTest For me, this works. If I leave off the geode-core: part I get a failure from every other subproject (geode-core, geode-assembly,...) no matter which test target I run. -Dan On Tue, May 17, 2016 at 1:51 PM, Kirk Lund <[email protected]> wrote: > Specifying -Dtest.single now always fails no matter which test (UnitTest) > is specified. The integrationTest and distributedTest tasks still work with > .single. Only test (UnitTest) is effected. > > It fails in :buildSrc:test despite specifying geode-core:test so I'm > guessing it was the addition of buildSrc that broke it... > > <klund@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [687]$ ./gradlew > -Dtest.single=StringUtilsJUnitTest geode-core:test > > :buildSrc:compileJava UP-TO-DATE > :buildSrc:compileGroovy UP-TO-DATE > :buildSrc:processResources UP-TO-DATE > :buildSrc:classes UP-TO-DATE > :buildSrc:jar UP-TO-DATE > :buildSrc:assemble UP-TO-DATE > :buildSrc:compileTestJava UP-TO-DATE > :buildSrc:compileTestGroovy UP-TO-DATE > :buildSrc:processTestResources UP-TO-DATE > :buildSrc:testClasses UP-TO-DATE > :buildSrc:test FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':test'. > > Could not find matching test for pattern: StringUtilsJUnitTest > > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > > BUILD FAILED > > Total time: 0.782 secs >
