Part 1 - Smart Test Automation: Intuitive Enhancement over Reactive Rectification

Summary: It is an original paper, written by Debi Prasad Mahapatra, that talks about (and tries to conceptualize) a Predictive Method to drastically shorten the cycle-time and total-time pertaining to the Test-Fix-Retest cycle(s) in large-scale Test and Workflow Automation Projects. This concept intends to provide a mechanism (method | technique) that can be effectively used to optimize Time and Effort factors involved in a Test | Workflow Automation Project. Essentially, using this method, a Test Automation Project can be completed sooner with way less amount of effort and resources.

Abstract: This is an original paper based on the author’s experience on a real life large-scale Test and Workflow Automation Project. It was ascertained that the cycle-time pertaining to “Test – Fix | Optimize – Retest” cycle was a substantial portion of the total project lifecycle. And, universally, that is the case in most of the contemporary large-scale GUI-Based Test Automation projects. The goal was to shorten the cycle-time pertaining to the Test-Fix-Retest cycle! A method was devised on an experimental basis. The method was put to use and it really worked to save a substantial amount of time. Despite so many tough challenges, delivery to the customer could happen on time without compromising on quality. This paper intends to describe that method and the way it was implemented.

What questions does this paper intend to answer?

1. How is it possible to apply this method (technique | practice) to almost any large-scale Test Automation assignment (project)?

2. How to save substantial amount of valuable time in the complete lifecycle of a typical Test Automation Project?

3. How to streamline project workflow to reduce human-effort?

4. How to maintain quality (Test Coverage of Automated Test Solution – Testing the TEST enough!) of delivery under a critical (crunch) situation?

Test Automation, over the past decade or so, has gained substantial popularity and importance because of the advantages it has the potential to offer. At the least, it represents and replicates human intelligence in the context of Software Testing. At its best, it makes human life easy and comfortable by taking up tasks that human hands would otherwise do. However, before it makes life easy, it takes substantial time, effort, creativity and dedication to build a good Automated Test Solution (ATS). Test Automation prevails to reduce, ultimately, the time and effort consumed (used) in testing something (software, in this case). 

Would not it be really beneficial if we had a way to reduce the time and effort consumed in building an Automated Test Solution? So, essentially, that would not only save us time and effort when we use that Solution, but when we build (create) that Solution as well. This paper intends to describe a method that has the potential to drastically reduce the time and effort consumed in building an Automated Test Solution. This method, the author believes, can be effectively replicated and used in almost any real-life large (and medium) scale Test Automation assignment (or project).  Next Page >>