Most of the information that testers produce is an output of what, over recent years, has come to be called checking. The strict definition of checking (compared to the other testing that testers perform) isn’t quite settled yet, but the popular view of checking is that it is a mechanical or procedural, pre-meditated and error-prone and, in principle, it could be automated.
It’s an obvious question, why do we ask human beings to perform an activity that is obviously better done by tools?
Many organisations have tried to automate manual checking but often, the promise of automation is not realised. The most common mistakes made are over-ambition and unclear goals: You cannot automated every check; automated checks solve a different problem to ‘manual’ checking.
This session sets out how we could eliminate hands-on feature checking. We must focus our attention on what we will call a feature and understand our purpose. By redistributing our testing, up-skilling our testers and working closer with developers, Better software with fewer, smarter testers will be the outcome.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?