infra-testing-talk

You can find here the slides and the sample code of my talk "Testen von und mit Infrastruktur" that I presented on BaselOne at 17th October 2019.

Simulate Infrastructure in Software Tests

All code sample for simulating infrastucture in software tests are in infra-testing-demo-app. The code samples are tested with Java 11, embedded in a Spring Boot 2.1.8 skeleton. Following test libraries are used:

JUnit 5.5.2 including JUnit 4 (JUnit Jupiter Vintage)
AssertJ 3.12.2
MockServer 5.4.1
Wiremock 2.25.0
Greenmail 1.5.10
Testcontainers 1.12.2
REST assured 4.1.1
Spock 1.3

Tests against own REST API

The test class StarWarsMovieControllerITest shows how to test own REST API with Spring MVC and REST assured.

Mock REST dependencies

The test classes StarWarsClientMockserverTest, StarWarsClientWiremockTest and StarWarsClientMockserverGroovyTest show how to mock dependencies to a REST API with MockServer or Wiremock.

Testing interaction with E-Mails

The test class MailClientTest shows how to test interaction with e-mails (currently only sending) with Greenmail

Testing interaction with Database

The test class PersonRepositoryJUnit4/5/SpockTestshows how to test the repository logic including the database that is used in production with Testcontainers. Test class DBMigrationJUnit4/5Test shows how to test the database migration script inside my Maven build.

Infrastructure as Code Testing

All code samples for infrastructure as code testing are in infrastructure-as-code-testing. The code samples are tested with Bash, Ansible 2.8.5 and Docker 19.03.2.

Following test tools are used:

Shellcheck 0.4.6
Ansible-lint 4.1.0
yamllint 1.15.0
Serverspec 2.41.3
Testinfra 3.2.0
hadolint 1.17.2
Container Structure Test 1.8.0
Molecule 3.0a4

Setup Test Infrastructure

I prepare some Vagrantfiles for the setup of the test infrastructure if necessary. The only prerequires are that you have to install VirtualBox and Vagrant on your machine. It is tested with Vagrant 2.2.5 . Then follow these steps:

Open a CLI and go to the location of the file Vagrantfile.
Call vagrant up. Vagrant will download the necessary image for VirtualBox. That will take some times.

Hint: Public and private keys can be generated with the following command: ssh-keygen

Shell Scripts

Shell script sample is in infrastructure-as-code-testing/shell. This is also the location for the next CLI calls.

Code quality check for the shell script: shellcheck setup-svn.sh.

Ansible Playbooks

Ansible playbook samples are in infrastrucutre-as-code-testing/ansible. This is also the location for the next CLI calls.

Code quality check for Ansible playbooks with Ansible-lint: ansible-lint *.yml
Code quality check for YAML file in common with yamllint: ỳamllint *yml
Running ansible playbooks against the test infrasructure (see chapter 'Setup Test Infrastructure' above):

ansible-playbook -i inventories/test -u vagrant setup-db.yml # MySQL setup
ansible-playbook -i inventories/test -u vagrant setup-app.yml # Apache Tomcat setup

Running serverspec tests against a provisioned VM: rake spec
Running testinfra tests against a provisioned VM:

py.test --connection=ansible --ansible-inventory inventories/test -v tests/*.py

Molecule

Molecule is an aggregator over some testing tools for Ansible roles.

For running Molecule go to infrasructure-as-code-testing/ansible/roles/tomcat and run molecule test

Docker Image

Dockerfile sample is in infrastrucutre-as-code-testing/docker. This is also the location for the next CLI calls.

Code quality check for Ansible playbooks: hadolint tomcat.df
Build the Docker image based on tomcat.df:

docker build -t sparsick/tomcat9 -f tomcat.df .

Running the Container Structure Tests (prerequisite Docker image is built before):

container-structure-test test --image sparsick/tomcat9:latest --config tomcat-test.yaml

legap / infra-testing-talk