Myths of Scriptless Test Automation

Myth 1: Tool automation engineers are now no more required

Truth 1: Being scriptless in no way suggests doing away with the automation tools. Scriptless works in collaboration with underlying automation tools like QTP, Functional Tester, Selenium and many others. Even though, the scriptless approach ensures manual testers and SMEs can automate test cases, scriptless automation goes beyond just automating test cases. A testing team needs tool automation experts to build, maintain, and enhance automation strategy, technology assets, object management, and much more.

Myth 2: Scriptless is just about putting functions in a sequence

Truth 2: Scriptless is an approach to make test automation scalable without increasing cost on people, tools, technology, and infrastructure. It ensures the impact of change is well managed without compromising on quality and go to market time.

It is true that scriptless makes automating test cases very easy. It eliminates the complexities of the test tool. It is a layer residing on top of any test automation tools. This layer houses all the code assets that are ready to be used and are re-usable. They are not scripts for test cases but scripts at a granular level that can be scaled across technology, automation tool, and applications.

So, going scriptless is about getting these code assets in place that can be sequenced in more than one ways to build an automated case for any application built on any technology framework and that can be tested by any test automation tool. Scriptless should foster scalability and flexibility.

Myth 3: Makes automation a manual tester’s responsibility

Truth 3: Even though with scriptless automation manual testers can now quickly automate test cases, test automation still remains a forte of test automation engineers. As I mentioned above in my first point, scriptless automation goes beyond just automating test cases. A testing team should ideally compromise of about 20% of test automation experts. What if you need to change the code asset that has been used to build multiple test cases when the behavior of that particular UI object class has changed? Scriptless is an approach to build an optimized test automation process. Hence, it is therefore not only a manual tester’s responsibility – but the entire team’s.

Myth 4: Once built is built for life

Truth 4: Going scriptless is about building an open architecture to institutionalize the framework allowing adaptability and flexibility to changes in tools, technologies, processes, etc.

Source by Ravi Nukala