It occurs to me this evening that when test plans, test scripts, and testers look for particular problems with excessive focus, they do so at the expense of peripheral vision.
It occurs to me this evening that when test plans, test scripts, and testers look for particular problems with excessive focus, they do so at the expense of peripheral vision.
You can find an extensive list of presentations and courses that I've taught, including the slides and speaker notes for many of them, here.
I'll be presenting a keynote address at the RIM Test Automation Conference, August 18-19, in Waterloo, Ontario.
I'll be visiting Dublin, Ireland to teach a public offering of Rapid Software Testing September 13-15, 2010 at Xilinx, Citywest Business Park. The Software Skillnet people have asked me to mention that "This class is being grant aided by Software Skillnet". There are very substantial discounts on the course for Skillnet members. You can book your place by following the instructions and then sending email to Susan Kelly.
I'll be presenting a tutorial and a keynote at Agile Testing Days in Berlin, Germany, October 4-7, 2010.
The Software Test and Performance Conference will be held in Las Vegas, Nevada this year. Despite that, I'll be there, giving a two-day tutorial in Rapid Software Testing October 17 and 18, and a keynote address on October 19. The conference continues through October 21.
On October 21, I'll be giving a keynote talk at TesTrek in Toronto, Ontario. The entire event runs October 18-21.
Rapid Software Testing will be offered again in London, England, again through Electromind, the week of November 1, 2010..
I'll be at EuroSTAR for the fourth year in a row. This time, I'll be presenting a half-day tutorial on test framing the skill of linking risk, oracles, coverage, and tests—and your account of them—in a coherent logical framework. The conference is in Copenhagen, Denmark, November 29 through December 2.
A very astute observation in my opinion.
I’ve worked with two kinds of tester in my career: the pragmatic kind who uses scripts as a guide deviating from them more or less depending on the nature of the product. And another kind who seem to think that a good solid test script and the rigid following of it is the end goal of the test process.
Guess which projects have been more successful (and certainly less tense!).
When i was twelve, i read something from Bruce Lee about peripheral vision, so i *trained* myself to observe what was happening around the edges of what i was looking at. It helped alot in sport because i was able see the play evolve in a *broader* way (much like switching your viewing habits to a widescreen TV).
I’ve tried to use test scripts as guide and quite often would deviate from the script if i noticed something. Other times when i’ve been stuck in a rut, the test script became a checklist to tick off and i missed anything that might be vaguely interesting.
Today, i find that using an Exploratory Test approach helps resolve the lack of peripheral visin syndrome and if i have to use scripts, i am aware of becoming stuck in the ‘rut’.