CrateTestCluster is not terminated when a unit test fails

[mkleen]

import io.crate.testing.CrateTestCluster;
import org.junit.AfterClass;
import org.junit.BeforeClass;
import org.junit.Test;

import static org.hamcrest.MatcherAssert.assertThat;
import static org.hamcrest.CoreMatchers.is;

public class ShutdownTest {

    private static CrateTestCluster testCluster;

    @BeforeClass
    public static void setUpClusterAndAgent() throws Throwable {
        testCluster = CrateTestCluster.fromURL("https://cdn.crate.io/downloads/releases/nightly/crate-latest.tar.gz")
                .keepWorkingDir(false)
                .build();
        testCluster.before();
    }

    @AfterClass
    public static void tearDown() {
        testCluster.after();
    }

    @Test
    public void test() {
        assertThat(true, is(false));
    }
}

[amotl]

Hi. We will probably want to run a new release after adding GH-87. In this spirit, let me ask if this one is still an issue?
If so, can it be fixed, or shall we focus on providing a first-class Testcontainers implementation instead?

• Software Testing with CrateDB
• [Java] crate-java-testing cratedb-examples#342

The first link refers to the canonical documentation page about test layers for CrateDB, the second one is a reminder that crate-java-testing is missing on it.

My evaluation is that both variants can be used, while the Testcontainers thing is currently a future-looking thing, while even some of our own artefacts are actively using crate-java-testing. In this spirit, I think it should be fixed when possible.