Dan and I have discussed moving dunit from geode-core/src/test to its own submodule geode-dunit. This way the framework would be usable by Geode users for their own apps.
Right now dunit refers to DistributedSystem and Locator which are in geode-core/src/main. We'd have to alter dunit to use a more generic abstraction for this dependency so it's not a circular dependency. If we were to make that abstraction general enough to allow for different plugins then we could open it up for non-Geode uses (someone who wants to use it for Zookeeper would then have to write a plugin or limit their use to just the RMI connectivity in the dunit VM API). On Thu, Jan 19, 2017 at 2:55 PM, Bruce Schuchardt <bschucha...@pivotal.io> wrote: > Looking at the current code a little more I see that the base class > JUnit4DistributedTestCase is tied to Geode. You would need to create an > equivalent to it that doesn't refer to Geode and then base your test case > on that. > > There is a little documentation here: https://cwiki.apache.org/confl > uence/display/GEODE/Distributed-Unit-Tests > but it wasn't updated when DistributedTestCase/CacheTestCase were > replaced with JUnit4DistributedTestCase and JUnit4CacheTestCase. > > > Le 1/19/2017 à 2:32 PM, Roman Shaposhnik a écrit : > >> On Thu, Jan 19, 2017 at 2:30 PM, Bruce Schuchardt >> <bschucha...@pivotal.io> wrote: >> >>> Hi Roman, >>> >>> DUnit is an RMI-based system. The only ties it has to Geode are that it >>> creates a Locator before running tests. >>> >> Is there a separate doc for it? Suppose I wanted to use DUnit to test, >> lets >> say, Zookeeper -- where would I start so that I can write my first >> testcase? >> >> Thanks, >> Roman. >> > >
