hans-henrik olesen - what to automate and what not to automate
TRANSCRIPT
Hans-Henrik Olesen & Gauri Varma Heise
What to Automate and What Not to Automate
Agenda
• Motivation
• Collection of Data
• Key Points
• Questions
Motivation
• Prior experience made us interested in which considerations should be taken into account when automating.
• What factors make test automation a success.
• Tired of tool centric automation focus and very little attention given to the approach and the decision making process.
Collection of Data
Id Type of Software Project Size Dedicated Testers
eFPI Validation of data and workflows between 3rd party software
20 persons No
Sitaware Command and Control System
70+ persons Yes (14)
Danske Fragtmænd PDA based booking system
9 persons No
EPJ Fully integrated electronic patient record solution
40+ persons Yes(6)
Jobnet Web based solution for the National Labour Market Authority
14 persons Yes(1)
Key Points
• Structured Decision Making (SDM)
• Integrate thoughts on test automation as early as possible.
• Define the amount automation according to the software type
Key Points
• Automated test can’t find defects you haven’t already thought of.
• Don’t think of test automation as only a way of reducing time spent on testing but rather as a way of relieving the testers from doing trivial testing.
Questions?