Poland _ Cognifide
We can treat almost every element of our systems as code. That includes the underlying infrastructure, its configuration – and our delivery pipelines.
We can treat our delivery pipelines as code; from the way the developers push their work to the repository, to the way we make it available to our users on production. We can build a direct, concrete and testable implementation of our delivery process. Can we use our well-honed testing skills to test a delivery pipeline?
In this workshop, we will take an example application and design and implement all stages of its delivery pipeline using tools like Docker, Jenkins and Jenkins Pipelines. We will:
The exercises will help you understand the techniques behind the delivery process, and give you more insight in the way you might do the same within your own project and team. This session is for anyone who wants to dive into the area of CI/CD pipelines design and implementation, and into the skills that help us as QA specialists to understand the design, implementation and testing of delivery pipelines. The exercises will require some basic knowledge about Docker.
An experienced QA Engineer. Test automation specialist, trainer, and evangelist. Technical testing, CI/CD, and Test/DevOps enthusiast. A QA Lead responsible for quality-related aspects throughout the project lifecycle, now also a consultant helping others with automating their work. He regularly searches how to improve even the good solutions.
Embraces his love of discussing things as one of the DebatQA co-hosts. Speaker at various meetups and conferences. Part of the TestWarez 2018 programme committee. Blogger at automatingguy.com.