CI/CD for Automation Testers

CI/CD pipeline or Continuous Integration/ Continuous Deployment is the backbone of today’s app deployment process.

A pipeline is a workflow which consist of multiple jobs to deliver the software to the customers.

Version control > Build > Unit tests > Deploy > Automation tests > Deploy to production

Above representation is the basic flow of the whole pipeline process that represents how software will move along the different stages before it reaches the customer.

As an Automation tester, we majorly needs to focus on Continuous Integration.

Continuous Integration process after the planning stage. In this stage, developer integrate their code very frequently (multiple times a day) in some central source code repository. Each integration is verified by automated build and automated tests.

Major key benefit of continuous integration

1. Continuous feedback on the recent changes in code.

2. Detects the errors early and quickly.

3. Cost effective

4. Decrease testing time and QA team can invest more time in building quality culture.

Continuous delivery VS. Continuous deployment

Continuous delivery is an extension to the Continuous Integration process.It deploys all the new code to the testing or production environment after going through the automated build stage.In other words, we can set an automated release process as per our requirements(daily, weekly or fortnightly) with just a click of a button.

However, Continuous Deployment is an add-on to the Continuous Delivery process. In this every change that passes all the stages of the pipeline is released to the customers.

Cheers!! 🍻