+1 I think I'm in favor of all of these changes as well. I don't know
anything about buildship though.
I do have a few dunit changes on a feature branch that I'd like to get
merged to develop before we move dunit out of geode-core. I'll try to wrap
up these changes by Tues or Wed.
On Mon, Apr 16,
+1 For a cleaner public dunit API.
I am changing my proposal to rather create "geode-test" sub-module by
combining geode-junit, geode-old-versions, and dunit test
framework(extracted from geode-core).
For eclipse users, I would recommend the use of buildship (rather than
gradle eclipse plugin) an
+1 Seems like great idea!
A couple thoughts - I think it would help our users if we make dunit API
very clean and abide by our backwards compatibility rules for that API as
well. It would suck to write a test suite that keeps breaking on every
version of geode.
I think you still might run into so
All,
Geode's dunit framework can provide an easier way to write integration
tests for any server-side extensions or server-side application code.
Currently the dunit framework is not a published artifact, so developers
cannot write distributed tests. So the proposal is to move all dunit
framework
