Voxxed Banff 2018 : Containers & Integration tests

@ i x c h e l r u i z # Vo x x e d D a y s B a n ff
INTEGRATION TESTS &
CONTAINERS
A SUCCESS STORY!

INTEGRATION TESTS &
CONTAINERS
HEROIC DRAMA

INTEGRATION TESTS

LHC : Testing facilities

OCTOBER 2008

OCTOBER 2008
✓24 dipole magnets of 30
dipole magnets

CONTAINERS

“ “
Write once, run everywhere
WORE

“ “
Package Once, Deploy Anywhere
PODA

Development
Production
Tests

PROJECT “HYDRA”
PRODUCT

PROJECT “HYDRA” DATA SHEET
Server : Spring-boot v1.5.1
Client : (2) Webapps polymer v 0.5 - v 2.0
Product: Griffon 2.3.0 Application : JavaFX (UI)
Build tool : Gradle v3.5
Database: H2 & Postgresql 9.4
VC Database: Flyway

VC Database: Flyway
Production
Development

H2 POSTGRES

H2
✓In memory database
✓Spring-boot integration
✓Easy to setup

BUT
✓is not Production
✓(compatibility mode is not
enough)

USE POSTGRES
CONTAINERS

COMMAND LINE

$ docker run --name my_psql
→ -e POSTGRES_PASSWORD_FILE=/postgres_password
→ -e POSTGRES_USER=psql_user
→ -e POSTGRES_DB=psql_db
→ -v /Users/ixchelruiz/.config/postgres_passwd:/postgres_password
→ -p 5432:5432
→ -d postgres:9.4

DOCKER-COMPOSE

DOCKER-COMPOSE.YML
version: '3.1'
services:
db:
image: postgres:9.4
restart: always
environment:
POSTGRES_USER: psql_user
POSTGRES_PASSWORD_FILE: /postgres_password
POSTGRES_DB: psql_db
ports:
- "5432:5432"
volumes:
- /Users/ixchelruiz/.config/postgres_passwd:/postures_password

Success!
Developers

CLIENT ENVIRONMENTS

POSTGRESQL CONFIGURATION

CLIENT
✓Postgres configuration for
different environments
✓ Test
✓ User acceptance
✓ Production

REVIEW IDEAS

DEVOPS

“ “
Snowﬂake server vs Phoenix server
— Martin Fowler
Puppy

SNOWFLAKE PUPPY
✓Evolve with time
✓“unique and special”
✓Difficult to reproduce
✓ Nurse back to health

PHOENIX SERVER
✓Automatization tools
✓Security patches
✓Configuration

PHOENIX SERVER
✓Automatization tools
✓Security patches
✓Configuration
Base Images

GRADLE / MAVEN
DISCLAIMER

GRADLE-DOCKER-PLUGIN

https://github.com/bmuschko/gradle-docker-plugin

CREATE CUSTOM IMAGES
OVERKILL?

CREATE CUSTOM IMAGES
OVERKILL?
YEAH!! KIND OF.. BUT

apply plugin: 'com.bmuschko.docker-remote-api'
import com.bmuschko.gradle.docker.tasks.image.Dockerfile
import com.bmuschko.gradle.docker.tasks.image.DockerBuildImage
task createDockerfile(type: Dockerfile) {
destFile = project.file('build/mydockerfile/Dockerfile')
from 'ubuntu:12.04'
maintainer 'Benjamin Muschko "benjamin.muschko@gmail.com"'
}
task buildImage(type: DockerBuildImage) {
dependsOn createDockerfile
inputDir = createDockerfile.destFile.parentFile
tag = 'bmuschko/myimage:latest'
}

Success
Infrastructure

AND NOW
THE PROJECT

AND NOW
THE PROJECT
YAY!!

VC Database: Flyway
Production
Development
BO
M

FLYWAY
VERSION CONTROL FOR YOUR DATABASE.

MIGRATE
SCHEMA & DATA

✓ New Release
✓ Flyway migrating schemas &
data

OPPSSS!
✓ New Release
✓ Flyway migrating schemas &
data
✓I made a bubu

TEST

TEST
LOCALLY

TEST
LOCALLY
MIGRATION SCHEMA & DATA

TEST
LOCALLY
MIGRATION SCHEMA & DATA
SANITY CHECK

DOCKER-COMPOSE.YML (VERSION 1)
version: '3.1'
services:
db:
image: postgres:9.4
restart: always
environment:
ports:
- "5432:5432"
volumes:
healtcheck:
test: ["CMD-SHELL", "pg_isready -U postgres”]
web:
image: tomcat:8-jre8
ports: 8080
depends_on:
- db

OR
WAIT FOR IT!

DOCKER-COMPOSE.YML
version: '3.1'
services:
db:
image: postgres:9.4
restart: always
environment:
ports:
- "5432:5432"
volumes:
web:
depends_on:
- db
command: ["./wait-for-it.sh", "db:5432", "--", “cmd"]

DOCKER-COMPOSE-PLUGIN
(GRADLE)

https://github.com/avast/gradle-docker-compose-plugin

buildscript {
dependencies {
classpath "com.avast.gradle:gradle-docker-compose-plugin:$version"
}
}
apply plugin: 'docker-compose'
dockerCompose.isRequiredBy(test)

Success
Developers

INTEGRATION TEST
CI : WITH A TWIST!

CI
✓Port conflict
✓Environment variables

buildscript {
dependencies {
classpath "com.avast.gradle:gradle-docker-compose-plugin:$version"
}
}
apply plugin: 'docker-compose'
dockerCompose.isRequiredBy(test)
test.doFirst {
// exposes "${serviceName}_HOST" and "${serviceName}_TCP_${exposedPort}" environment variables
dockerCompose.exposeAsEnvironment(test)
// exposes "${serviceName}.host" and "${serviceName}.tcp.${exposedPort}" system properties
dockerCompose.exposeAsSystemProperties(test)
// get information about container of service `web` (declared in docker-compose.yml)
def webInfo = dockerCompose.servicesInfos.web.'web_1'
// pass host and exposed TCP port 80 as custom-named Java System properties
systemProperty 'myweb.host', webInfo.host
}

CI
✓Zombie containers
✓Force compose down
✓Configuration it’s different
✓Development
✓Testing

✓ Automatic discovery of local docker environment
✓ Pull images or build from Dockerﬁle
✓ Start/stop container
✓ Wait for it to be ready (log string / listening port / protocol-
speciﬁc)
✓ Port mapping
✓ Clean up

✓ Manage Dockerized external dependencies via a Java object facade
✓ JUnit integration
✓ Starts/stops containers for each class/method
✓ Reliability:
✓ start from clean state
✓ isolated instances
✓ port randomisation
✓ tag-based versioning
✓ Java JUnit support; Spock, Scala and Python wrappers/forks

DEMO

THANK YOU
QUESTIONS OR FEEDBACK?
PLEASE FILL THE SURVEY! PING ME! TALK TO ME!

Voxxed Banff 2018 : Containers & Integration tests

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (19)

Similaire à Voxxed Banff 2018 : Containers & Integration tests

Similaire à Voxxed Banff 2018 : Containers & Integration tests (20)

Plus de Ixchel Ruiz

Plus de Ixchel Ruiz (10)

Dernier

Dernier (20)

Voxxed Banff 2018 : Containers & Integration tests