Quality Gates in Test Automation
Our organization adopted the CI/CD model for all product validation tasks just over 1 year ago with automated testing being primary step in the pipeline. We discovered that test automation eventually became a bottleneck within the pipeline due to its flakiness and constant maintenance. We determined a need to treat test automation development similar to product development. This allowed us to define multiple Quality Gates in test automation development by utilizing our own CI/CD pipeline. Now, we have tremendous confidence in our test automation and its stability in product validation. Every new check-in of test automation code goes through quality gates and the final test automation build is delivered only after passing all the quality gates within the Test Automation pipeline. Biggest lesson is to transform our mindset by treating test automation development as we do product development. If we are adopting best practices for product development such as validation within a CI/CD pipeline, security and static code analysis scans, along with the use of quality gates then we should adopt these same practices for test automation development. At the end of the talk, conference attendees will know exactly how they can transform their test automation code through implementation of various toolsets, along with use of quality gates in the test automation CI/CD pipeline to achieve robust, stable, releasable automation.