How do you measure automation success?

(Vishal Dutt) #21

We may check the automation success on several parameters if we talk about different software testing companies approach. Most of the projects are now being tested by automation only as it saves lots of time and efforts.

  • One of the ways to check the automation success is by running the automated tests on daily bases with the help of Jenkins scheduled jobs which we call CI/CD/CM (Continuous integration/Continues development/Continuous Monitoring) process. On the basis of these results in Jenkins pipeline, the success of automation can be measured. If the pipelines are appearing as green consistently that means the code is stable because most of the time it happens that the same code is ran on different environments.
  • Next parameter, we can take here into consideration can be regression testing where we have to execute the automated code on different deployed instances/builds to verify the existing defects. If the code is able to produce/check the defects that is again can be counted as success of automation. As this automation process is also saving the time and reducing the manual efforts, it should be the priority that code is written with logic and should be robust so that automation brings the correct results. With such code, we will always be able to find new defects in the application, and finding defect with the help of automation is considered as a great thing.
  • The another important parameter can be noted as change of functionality in the application. For the little change in the functionality, the manual person need to execute the whole test cases just to make sure functionality is working fine, but on the other hand if we are having an adaptive framework, we just need to change few methods, locators and rerun the code. This will bring up the results and will save a lot of time.

Hope this is helpful for you.