Andrei was born and raised professionally in the Agile era, with multi-industry experience: banking, real-estate, telecom, insurance, internet security and marketing throughout a handful of platforms: back-end, front-end, mobile & desktop. He has always found himself challenging state of the art of Software Development, classical QA and testing approaches, throughout the different activities he has engaged with: from manual to automation testing, handling product functional to non-functional requirements, executing to architect solutions implementations, leading platform initiatives and leading QA departments and activities.
In an EverythingAsCode context, Quality professionals should expand their reach and go beyond functional test. Our CI/CD Pipelines are prone to introduce defects. Are we testing them enough?
Session Abstract: CI/CD Pipelines are already part of our code bases – compiling, testing, creating images, deploying, handling env variables, reporting, and are no longer just a series of simple cascaded actions: they have outputs, if statements, functions. They are complex. A recent study in the industry concluded that testing early becomes less useful as infrastructure complexity rises. And they are right. That’s why we need to shift left also testing the infrastructure and, bring in test automation.
This is a highly practical session. We’ll discuss briefly the why – take a popular CI/CD cloud solution (eg: Github Actions) – look at a simple predefined CI/CD workflow yml -> and design one Test Case for it. Execute it manually. Automate that test case using the same workflow (using the Github Action Test automation framework which I’ve built to solve for me the same problem: https://github.com/therussiankid92/gat) – tips & tricks for developing testable CI/CD Pipelines – conclusions What will be discussed here can be applied for any tech stack, not just for the one mentioned as the philosophy is the same.
Previous knowledge on what is a CI/CD Pipeline will be an advantage.