Chidambaram Vetrivel

Title: Agility with Continuous Testing using CI

Abstract:

Agile practices with Continuous Integration and Continuous Delivery (CI/CD) pipeline approach have increased the efficiency of projects.

Enterprises need to move faster and more flexibly in application development, testing and QA to keep up with the competition and meet customer expectations for shorter cycle times and higher service levels.

This requires integrating the efforts of their development and QA teams and automating manual processes wherever possible

Once you have all your code and changes going to the same place, you can run some processes on that repository every time something changes.

This could include:

1.Run automatic code quality scans on it and generate a report of how well your latest changes adhere to good coding practices - SonarQube

2.Build the code and run any automated tests that you might have written to make sure your changes didn’t break any functionality

3.Generate and publish a report to get an idea of how thorough your automated tests ran through

4. Can Integrate more changes to the Pipeline

These simple additions allow the developer, to focus on writing the code.

Your central repository of code is there to receive your changes while your automated processes can build, test, and scan your code while providing reports.

We have 4 Verification or Check Points

1. DevOps Verification

2. Back-end Verification

3. Front end Verification

4. QA Verification

And we have a standard Checklist for each Module for Verification and we incorporate the changes to the Pipeline to ensure it follows the standards.

In case of any issues on any Module it sends the notification back to the Developers, so they fix it quickly as the turnaround time is quite negligible.

Once it passes the phase it generates a Standard report that includes all the Modules and its Verification pointers for better understanding.

Also, it shares a notification once build is created.

Continuous Delivery (CD) process optimizes & automates the whole software deployment, to facilitate a smooth operation of delivering a software product to the market.

Through this approach, a codebase can be delivered any time & the software will be on schedule.

The key goals of CI are to find and address bugs more quickly, improve software quality, and reduce the time it takes to validate and release new software updates.