Tangentially related, we have a test-by-category.gradle. Is anyone using any of those targets? I suspect that many of these targets are no longer stable or correctly configured ever since we restructured tests around integrationTest / distributedTest / etc.
Running `./gradlew securityTest` locally, I got a CNF for the category org.apache.geode.test.junit.categories.SecurityTest, presumably because the classpath is configured differently for many of our test types. Should this gradle file and associated targets be removed, accepting the more-efficient -PtestCategory filter on `./gradlew integrationTest` et al as the "correct" way to filter on category? On Tue, Sep 25, 2018 at 1:10 PM, Kirk Lund <kl...@apache.org> wrote: > Awesome! Thank you. > > On Tue, Sep 25, 2018 at 12:01 PM, Ryan McMahon <mcmellaw...@apache.org> > wrote: > > > This information is now in the TESTING.md in the Git repo as well FYI. > > > > Ryan > > > > On Tue, Sep 25, 2018 at 11:51 AM Anthony Baker <aba...@pivotal.io> > wrote: > > > > > Add a property like this on the command line when you execute a test > > task: > > > > > > -PtestCategory=org.apache.geode.test.junit.categories.GfshTest > > > > > > Anthony > > > > > > > > > > On Sep 25, 2018, at 2:21 PM, Kirk Lund <kl...@apache.org> wrote: > > > > > > > > I've made sure that all logging related tests have the LoggingTest > > > category > > > > but now I can no longer find any mechanism in our gradle files to > > execute > > > > all tests of a specific component category. Is there a way to run all > > > tests > > > > with this category or did this get deleted? > > > > > > > > >
