Allow creating a CuratorTestingServerExtension that starts the testing server in the constructor?

[sleberknight]

Background

The original (i.e. pre-GitHub) implementation of CuratorTestingServerExtension did the following in its constructor:

testingServer = new TestingServer(port);

The above is equivalent to:

testingServer = new TestingServer(port, true);  // here, true means to start the server *right now*

When we re-implemented this in kiwi-test, we chose to do this in the constructor:

testingServer = new TestingServer(port, false);  // here, false means we will NOT start the server now

And then in the beforeAll we called testingServer.start(). Doing it this way is more correct in the way JUnit Jupiter extensions should behave.

However, this caused an issue when testing Dropwizard services using the DropwizardAppExtension, specifically because Dropwizard does not follow typical Jupiter extension conventions. It looks something like this when we're using the Dropwizard extension and the CuratorTestingServerExtension:

@ExtendWith(DropwizardExtensionsSupport.class)
class AppTest {

  private static final DropwizardAppExtension<AppConfig> APP =
          new DropwizardAppExtension<>(App.class, ResourceHelpers.resourceFilePath("config-app-test.yml"));

  private static final int ZOOKEEPER_TEST_SERVER_PORT = 37_456;

  @RegisterExtension
  static final CuratorTestingServerExtension ZOOKEEPER_TEST_SERVER =
          new CuratorTestingServerExtension(ZOOKEEPER_TEST_SERVER_PORT);

  // tests...

}

But when using the kiwiproject extension, the above does not work because there is no way to ensure the Curator TestingServer starts before the Dropwizard extension launches the test application. As a result, the App classes under test can never connect to a the Curator testing Zookeeper server, so we end up mocking things like leader latches inside App by doing something like:

public static class MockLeaderLatchApp extends App {
  @Override
  protected ManagedLeaderLatch buildManagedLeaderLatch(CuratorFramework curator) {
    return mock(ManagedLeaderLatch.class);
  }
}

//  and then...

  private static final DropwizardAppExtension<AppConfig> APP =
          new DropwizardAppExtension<>(MockLeaderLatchApp.class, ResourceHelpers.resourceFilePath("config-app-test.yml"));

This is not ideal, and doesn't test the actual leader latch in the App class.

To allow us to use the Dropwizard extension and the Curator testing extension, we could add a new constructor in the kiwiproject CuratorTestingServerExtension that accepts a second argument that forces the testing server to start immediately, i.e. it would call new TestingServer(port, true).

While this is not the "correct" way to do most Jupiter extensions, we don't have a choice in this case if we want to use it with the (nonstandard) Dropwizard extension mechanism. So we might do something like:

  @RegisterExtension
  static final CuratorTestingServerExtension ZK_TEST_SERVER =
          new CuratorTestingServerExtension(ZK_TEST_SERVER_PORT, TestingServerStart.IMMEDIATE);

where ServerStart is perhaps an enum inside CuratorTestingServerExtension:

public enum TestingServerStart {

  /** Start the Curator TestingServer immediately. */
  IMMEDIATE,

  /** Start the Curator TestingServer when beforeAll is called (this is the normal JUnit Jupiter lifecycle) */
  BEFORE_ALL
}

Again, while this isn't ideal and not the recommended way, we would no longer need to create the MockLeaderLatchApp and mock things out when we're trying to do integration testing.

[sleberknight]

Created issue #239 from this discussion, so this is effectively closed.