Test automation used to be a luxury. Since nowadays improving product quality, reducing costs, shortening time-to-market combined with more frequent releases are an irreversible trend, test automation has become a necessity. "Have we been successful at test automation thus far?" Asking the question is answering it. We need to change our approach to test automation. Like Jerry Weinberg said: "When something is not working, use more of it" is wrong. Core of the approach is to act "Goal driven", not "Tool driven"; look beyond technical selection criteria. Approach test automation step by step. Define realistic objectives and develop the business case for test automation. Analyze the context and define the required test automation solution. Experience has learned that the first level of test automation is best described as "enabling testing to achieve its goals". Level 2? Mitigate more risks than without automation! The optimal level? "Fit for purpose" and "Fit for context", scalable and future proof. Ruud describes a practical approach to implement and improve your test automation. Take back valuable references and examples that enable you to implement test automation effectively and efficiently, tuned to your specific situation. Learn how test automation can play the role it deserves: an indispensable and tireless part of your testing. And by the way. Don't be afraid, the human part of testing cannot be automated (yet). Test automation, if done well, enables the tester to focus on his essential role.
1. Goal driven, not tool driven
2. Automate what is necessary, not what is possible
3. Test automation levels:
a. enabling testing to achieve its goals
b. mitigate more risks than without automation
c. scalable and future proof
4. Translate "Fit for purpose" and "Fit for context" into concrete and tangible goals and actions
5. Let test automation finally play the role it deserves: an indispensable and tireless part of your testing.