In my earlier post, I support idea of being Script-less can help the testing industry. The idea behind this is really simple. Manual testers, SME’s will work in Graphical environment, can use simple English language while building scripts as there are built in libraries to support their work.
While this may seem nice and easy to imagine, this may not be the case while being practical. I shared experiences with automation testers and came to conclusion that there are some important things to consider:
We still need Script monks to support our work: Script less environment works on ‘Keywords’, which are simply another scripts. Those scripts need to maintain and keep consistent with change in product
Choice of tool to automate: This is an important task. Tool must be choose based on factors like Capability, Reliability, and Capacity. Learnability, Operability, Performance, Compatibility, Non-Intrusiveness. Refer Test Automation Snake Oilby James Bach. Download demo first. Doing a small pilot project for choice of tool is a good idea. Test tools often have bugs that matters to us.
Automated regression tests find a minority of bugs: (Lesson 110): James reported regression tests find about 15%of total bugs reported in his extensive work as tester. Regression functional tests find less than that. Those find more bugs during test development than executing tests later. Regression test will be more effective to find defect when we reuse them in different environment.
I thank Mr.Phil Kirkham from Expected results mentioning important problems coming in process.
1. Lessons learned in Software Testing by Bach,Caner and Pettichord.
2. Test Automation snake oil, Bach(1999)
3. Software test automation by Fewster and Graham
Few days before I have used Microsoft’s product called visual studio. It’s mainly a Developer tool which allows different wizards to visually design the GUI in the studio .In past developers hand code to make UI which is more time consuming, error prone and required very skilled person to do that job. The trick worked out successfully and Microsoft successfully able to achieve a Quantum jump into its productivity.
Now the Question is:
Can we use this concept for our testing work?
In testing, we use scripting for Regression testing mostly, which involves a lot of scripting. Automation experts having knowledge of specific language and tool are work for Automation of test cases.
Can we make this work script-less?
I did Google the word and found some interesting results. there are vendors who already working on the concept. (Wow!!).Two products that are providing very less or no scripting while test automation are Qualitia from Zensoft and Certify from Worksoft .Out of which Qualitia is Purely an Indian thing!
I studied some advantages of Script less test automation are:
Instead of a code editor, automation engineers/ or manual testers work in a graphical environment, where they can compose automated tests by selecting objects and actions from dropdown menus. They can also visually create conditions, iterations, etc.
Script less test automation provides a very easy to use interface – instead of learning a scripting language, or even a programming language, one gets to work on a drop‐down and Excel kind of user interface.
There is greater chance that Manual testing Community will accept this Script-less environment to work as they can easily Automate the Test cases without or less knowledge of scripting. Subject Matter Experts (domain knowledge people) will be easily automating the Test cases.
In this week I will come out with important pro’s and con’s of the Scriptless Automation..Stay Tuned !