You can customize and ignore unit tests with testcontainer

[liudaolunboluo]

My requirements are as follows: my unit test integrates testcontainer, but I only want to run this unit test locally. When using Maven to build on the jekins of the server, I don't want to run unit tests with testcontainer, but I don't want to run all unit tests. Based on this scenario, I propose several solutions:

1. Try catch has no exception in docker environment
2. Judge whether there is a docker environment in the current running environment. If there is no docker environment, the unit test of testcontainer will not be executed. At present, I use the "docker - V" command in the code. If the docker version can be returned correctly, there is a docker environment. If there is no docker environment, there is no docker environment. However, the same problem as 1 is that if testcontainer runs locally for the first time and the docker environment is not installed, the developer may not know why this unit test class is not running
3. I hope you can provide a configuration, parameter or option, such as "- dmaven. Skip. Test = true", which allows developers to decide whether to use testcontainer to perform unit tests in this Maven build

[rnorth]

Hi @liudaolunboluo

There's already something for this:

• firstly, have a look at the org.testcontainers.DockerClientFactory#isDockerAvailable method. This gives you a boolean result for whether Docker is available or not.
• JUnit 4 and 5 both support 'Assumptions', which conditionally ignore tests. If you put something like assumeTrue(DockerClientFactory.isDockerAvailable()) in your test method, or in a before/setup method, you can skip tests that require Docker.

Of course, we'd always recommend running all tests in CI as well as locally, so I hope that you might also be successful in doing this too!

[liudaolunboluo]

Hi @liudaolunboluo

There's already something for this:

• firstly, have a look at the org.testcontainers.DockerClientFactory#isDockerAvailable method. This gives you a boolean result for whether Docker is available or not.
• JUnit 4 and 5 both support 'Assumptions', which conditionally ignore tests. If you put something like assumeTrue(DockerClientFactory.isDockerAvailable()) in your test method, or in a before/setup method, you can skip tests that require Docker.

Of course, we'd always recommend running all tests in CI as well as locally, so I hope that you might also be successful in doing this too!

Thank you very much for your reply.

DockerClientFactory#isDockerAvailable () is not static. How do I call him in code?

[rnorth]

Ah sorry, DockerClientFactory.instance().isDockerAvailable()!

[liudaolunboluo]

DockerClientFactory.instance().isDockerAvailable()

Your reply is very helpful to me. Thank you very much

[rnorth]

You're welcome!