O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
Just like a tugboat brings containers safely to port, “Tugbot” will do the same for running quality Docker containers in production . Tugbot makes Continuous Testing REAL. It allows developers to write tests once - run anywhere. Any kind of test (including performance, chaos, and security) can be run with 5 lines in a “Test Container” Dockerfile. Leveraging the Docker LABEL and Docker unified API, we will show how this simplifies testing for services running in docker containers while standardizing results collected for analytics to continuously improve the quality of software.
Docker is changing the world for services and can do the same for testing Using Docker, we can take tests, package them in a container and deliver that content to any environment in the world.
Thanks to the fact that docker exposes uniformed API across any container we can do something very nice – we can do “tugbot”
In a docker hosted environment, tugbot can: Automatically discover any test container. Orchestrate the test execution (periodically or upon change event) Collect the test results And publish them to a centralized Result service store (Elastic Search) Visualize the resuls via ALM Octane and/or Kibana
5. Notice to fact that the “test container” could be a package that someone else wrote in the world and now I use it in my environment!
Configuring a test container is deadly simple. The first 3 lines is want you need to make your test package a testing container and the last two is what you need in order to integrate it with tugbot
Introducing "Tugbot" for Docker Containers
Neil Gehani - @GehaniNeil
Sr. Product Manager, Hewlett-Packard Enterprise
June 21, 2016
Continuous Testing + Deployment
Leverage Docker API
1. Discover Test
Containers 4. Publish
Results to ES
Open Source Contributions to Docker ecosystem
– “Tugbot” – Continuous Testing Framework for containers (CT made REAL)
– Open Sourced (Github)
– Published in docker’s weekly newsletter
– Containerized Docker Bench security testing - open source
– “Pumba” - Chaos testing inspired by Netflix simian army