Test automation has evolved to become a strategic and integral part of the software development process. Most of us start our test automation careers with record and playback. Over time, some of us move to data-driven test automation, but very few of us move towards the core where in the principles of design and development are applied to test automation. Test automation is like developing a system where test cases are requirements. The depth of thinking and planning that goes into test automation before hitting the record button is similar to developing software
Over the last 10 years, I have seen multiple Fortune clients struggle with automation and some of them eventually getting it right. For some of the projects that failed, we had the best test automation resources and a very stable manual testing practice but in spite of all this there was a huge gap between what was dreamt and what actually got realized. Over the period, we realized that the planning process is a key component for successful test automation. In 65% of the projects that failed the planning process and sequence of steps followed were the reasons.
Based on my experience, the automation process is:
- Why (Purpose)
- When (Stable Setup and Manual Process)
- Which (Tool Selection)
- What (Test Case Selection)
- How (Design)
We have written a detailed whitepaper “The Art of Test Automation” based on the test automation process above. Through this white paper, we have attempted to outline how to actually go about automating, planning, prioritizing and using better practices to ensure a lesser risk of complete failure in automation projects.
Some of the important test automation questions that this paper attempts to address:
- Why automation fails in spite of having technical resources?
- Is there a standard process to be followed for test automation?
- When to start and stop automation?
- Test selection criterion
Poonam Rathi | Test Consultant | Zen Test Labs