How To Make Quality Gates in CI/CD with GitHub

Continuous Testing is a fundamental part of delivering valuable software optimizing our effort. While it is a simple term, making the concept a reality requires a deep dive into implementation details.

We covered in previous articles the bottom-line reasons, challenges, and the core test automation elements in Continuous Testing. We will now share in a series of articles more concrete implementation elements.

This first article focuses on setting up Quality Gates within a CI/CD context. As a result, you can verify the application requirements as soon as possible using test automation. We will cover the following steps :

1. Clarify the architecture of the Quality Gates in CI/CD
2. Define the Quality Gates content with a Test Campaign
3. Implement the Quality Gates for the non-production deployment
4. Configure sanity checks and post-deployment tests
5. Continuously improve and shift-right afterward

You can follow this article by securing these prerequisites:

• GitHub account, if you don’t have one go here
• Cerberus Testing account, you can get a free cloud here
• An application under test on GitHub that you can fork here