Seconded. I've hacked around these limitations on our test suite as well, though (being far more lazy and, basically, not as good a person as you :-)) I haven't done any work to get patches out there. I'm pretty sure everyone doing any serious testing with ZK/Curator will inevitably run into these limitations.
On Thu, Jun 5, 2014 at 7:39 AM, Cameron McKenzie <[email protected]> wrote: > Curators, > Does anyone (Jordan?) know a compelling reason why the TestingServer() > starts the underlying server within the constructor, and has no way of > restarting the server? > > Not having this functionality makes it useless for testing connection loss > and reconnection. The underlying server classes that TestingServer wraps > up, support this functionality. > > Unless I'm missing something, I was going to raise a JIRA ticket and write > a patch to expose the start() and restart() methods of the underlying > server classes, and also create a new constructor that doesn't immediately > start the underlying servers. > cheers > Cam >
