The Rapid Software Testing Guide to What You Meant To Say – Michael Bolton
Michael


-
00:43:55
Description:
“I break the software.” “Cannot reproduce.” “We need a week to regress the new build.” “We have to do automation.” “It works!” From time to time, testers say things that they don’t mean, sometimes as a slip, and sometimes as a habit. Usually, there’s no malice or intention to mislead, but our clients may be deceived nonetheless. Worse, we can deceive ourselves.
Words are powerful tools for understanding and clarifying ideas, but like all tools, they must be used skilfully to achieve their purposes and to avoid trouble. In the Rapid Software Testing Guide to What You Meant To Say, Michael Bolton will report on some common expressions and patterns of speech that he considers risky, and he’ll offer ideas for using words more carefully and precisely.
This talk by Michael Bolton was presented at our software testing conference TestBash 2015 in Brighton
Previous Lesson:
Next Up:
-
What's In a Name? Experimenting With Testing Job Titles - Martin Hynie00:39:32
-
Re-running the ‘Are you a Mac or a PC? battle … for iOS and Android – Sally Goble & Jon Hare-Winton00:32:37
-
Automation in Testing - Richard Bradshaw00:28:30
-
Why I Lost My Job As a Test Manager and What I Learnt As a Result00:35:08
-
Quality doesn’t belong with the tester! – Maaret Pyhäjärvi00:31:18
-
Myths and Legends of Software Testing – Vernon Richards00:25:58
-
Getting Rid of Release Candidate Testing – Matthew Heusser00:27:32
-
Bug Detection - Iain McCowatt00:25:18
-
99 Second Talks - TestBash 201500:25:51