Extract Container runners from JUnit specific code

[raphw]

I want to suggest allowing Testcontainers as an API for starting and stopping Docker images from a Java application without depending on JUnit and to therefore remove the TestRule API from the container description that is JUnit (4)-specific.

I have started using Testcontainers.org for a standalone testklient and this works really nicely. With implementing my suggestion would allow for my use case but also offer a better integration for JUnit 5 that uses its own API or for using TestNG.

This would only require a minimum change in usage, one would for example write: new ContainerRule(new SomeContainer()) rather then new SomeContainer(). Other than that, the code is already segregated nicely.

Is this something you would consider to implement? I would be happy to offer the refactoring in this case.

[bsideup]

Hi @raphw,

Funny that you mentioned :)

There is an ongoing effort on it, see the proposal here:
rnorth/containercore#1

[raphw]

Awesome! Really looking forward to seeing that published. In our case, we can spin up a full environment of a microservice applications on any machine that has Docker installed. This works really nicely. Great effort.

[bsideup]

@raphw it's still on PR stage to receive some feedback, please, leave yours if you have something to add to it, that would be incredibly helpful!

Also, since you have really nice experience with fluent APIs (ByteBuddy FTW! :) ), maybe you can help us to design the next API for TestContainers 2.0. We have some ideas, but your input would be valuable ;)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.