Richtige Integrationstests mit Containern

A presentation at Developer Week in June 2019 in Nuremberg, Germany by Philipp Krenn

But the unit tests passed, so… https://twitter.com/Aaronius/status/ 933497253347463168

Ich mock mir die Welt widdewidde wie sie mir gefällt

https://www.monkeyuser.com/2018/ happy-flow/

! Unit tests, systems not under your control ! Test real datastore

Embedded Elasticsearch unsupported in 5.0+ https://www.elastic.co/blog/elasticsearch-the-server

! Often good enough ! Test real datastore, supported systems

Local installation Docker container Cloud

! “Good old approach” ! External dependency, parallelization

embedded-elasticsearch https://github.com/allegro/embedded-elasticsearch

Customization & Mappings .withPlugin(“analysis-stempel”) .withIndex(“cars”, IndexSettings.builder() .withType(“_doc”, getSystemResourceAsStream(“car-mapping.json”))

! IDE support, customization, custom lifecycle ! Custom integration

More embedded datastores https://github.com/flapdoodle-oss/ de.flapdoodle.embed.process

docker-maven-plugin http://dmp.fabric8.io

Dockerfile or Docker assembly <build> <from>java:8</from> <assembly> <descriptor>docker-assembly.xml</descriptor> </assembly> <cmd> <shell>java -jar /maven/service.jar</shell> </cmd> </build>

Build a custom image: docker:build Run container: docker:start docker:stop

maven-failsafe-plugin https://maven.apache.org/surefire/maven-failsafe-plugin/

! Standard or custom Docker image ! One instance for all tests, no IDE support

Dependency @ClassRule public static GenericContainer redis = new GenericContainer(“redis:5.0.5”) .withExposedPorts(6379);

Docker Compose integration @ClassRule public static DockerComposeContainer environment = new DockerComposeContainer(new File(“src/test/resources/compose.yml”)) .withExposedService(“elasticsearch_1”, ELASTICSEARCH_PORT, Wait.forHttp(“/”).forStatusCode(200));

Docker for Mac API: socat Linux: Multipurpose relay (SOcket CAT) https://github.com/alpine-docker/socat

Cleanup: Moby Ryuk https://github.com/testcontainers/moby-ryuk

[Ryuk] drops a Death Note, a notebook that allows the user to kill anyone simply by knowing their name and face https://en.wikipedia.org/wiki/Ryuk_(Death_Note)

! IDE support, customization, custom lifecycle ! Hacky configuration

ElasticsearchContainer https://www.testcontainers.org/modules/elasticsearch/

More languages Scala, Go, .net , Python , JavaScript , Rust * * * Early development * *

Selenium 2 / Webdriver VNC screen recording

$ docker run -it —rm -v $PWD:$PWD -w $PWD -v /var/run/docker.sock:/var/run/docker.sock maven:3 mvn —projects parent,4_testcontainers-custom test $ docker ps -a

Why not Mocking In-Memory Actual Datastore

Code https://github.com/xeraa/integration-test-demo

Philipp Krenn
@xeraa

1 / 69

Wie testet man mit Datenbanken? Mocking ist keine Option, da man das tatsächliche System testen möchte. In-Memory-Datenbanken, wie H2 oder HSQLDB, haben kleinere und größere Unterschiede und nicht alle Datenspeicher haben In-Memory-Geschwister. Verwendung und Test-Parallelisierung des eigentlichen Datenspeichers ist alles andere als ideal. Was ist also die Lösung? Es gibt zwei saubere Ansätze basierend auf Containern: Testcontainers und das Docker-Maven-Plugin. Aus den Tests können leichtgewichtige, wegwerfbare Instanz des jeweiligen Datenbanksystems gestartet werden. Dieser Vortrag zeigt ein praktisches Beispiel vor. Außerdem sehen wir uns das Testcontainer Modul für Elasticsearch an.

Resources

The following resources were mentioned during the presentation or are useful additional information.

GitHub Demo Code

Demoing multiple approaches of integration tests with Elasticsearch.

Richtige Integrationstests mit Containern

Link for this presentation:

HTML code for embedding:

Share on social media:

Resources

GitHub Demo Code