Letting your automated tests be the guardians for your quality success.

How do you know when your code is ready for production? At what point in time can you trust your automated tests enough to eventually deploy into production?

Companies make use of CI pipelines to help drive quicker execution of automated tests and ensure that code is of sufficient quality before deployment. Or at least that is what they are supposed to do. Too often, companies end up using CI pipelines to try and drive better software delivery but end up still delivering poor quality software into test environments and lose trust in the effectiveness of the pipeline process.

In this workshop we will have a look at the ideal structure of a CI pipeline and how to build the different quality gates into the pipeline to ensure that things like code coverage, security, automated test results and performance standards are all achieved before code is deployed to the different environments it is required. We will look at the structure of a CI pipeline, what the different stages mean and importantly how to enforce different metrics and targets automatically in the pipeline.

This workshop will start off with a talk about CI pipelines itself and the different quality gates that can be included to measure quality across the different stages before going into a more technical look at an actual CI pipeline in YAML code and then working to add the respective quality gates into the code through a variety of exercises.

This session will require some basic coding knowledge, but the focus is not on writing any automated tests, but rather in working with CI pipelines and using YAML as a base for the pipeline code. Even if an attendee is not keen in getting involved in DevOps pipelines having an understanding of quality gates in CI pipelines would still be beneficial.