Integration Of Automation Test Scripts With CI/CD Process
About Client
The client is one of the renowned names in the US Health and Wellness industry. The client provides comprehensive wellness solutions by creating a personalized health journey for employees of large employers nationwide.
Business Challenges
When we started the automation of the client project, the test execution was automation team dependent. Further, due to the different time zones of the development team and automation team, the execution results are delayed by at least 8- 10 hrs.
Venture7 Solutions
We have analyzed the entire automation process and proposed the CI\CD integrated Automation test strategy. We have chosen the Jenkin as a Continuous Integration tool as it is open-source with rich features of build management and reporting. We have started working on the scripts in Jenkin so that scripts can be executed through the command line. The test scripts are checked in on GitHub and fetched these scripts using the GitHub extension of Jenkins on a VM. Now based on the unit test framework, commands were formed and written in the Jenkins build pipeline. We have created different jobs based on the type of test like Smoke, regression, feature, etc., and named those in such a way that anyone can easily understand what this job is doing. Further, we have scheduled nightly regression with email reporting to stockholders for early bug detection.
Key Benefits/ Value Delivered
- Anyone from the client side can start the execution of test scripts in case no one is present from the automation team.
- Automatic execution report shared with stockholders.
- Daily Regression execution possible after this, once we are in the office we can check and let the stakeholders know about the build stability or if there is any bug. So early detection of bugs was made possible after this.
