Last month I got the chance to meet James Bach in a Rapid Software Testing training in Newcastle UK.
This training feels like catching grapes in a sandstorm as Greg said, because a lot of information is being exposed, and you are going to catch a fragment of it.
So I took notes :)
One of the conversations that happened was on books about testing. James said that some were misleading people to don't understand what testing was about.
So I asked James for a list of 5 books he though were pointing in the right direction:
An introduction to General Systems Thinking, by Jerry Weinberg.
Tacit and Explicit knowledge, by Harry Collins.
A Practitioners Guide to Software Test Design, by Lee Copeland*
Exploring Requirements, by Jerry Weinberg.
Perfect Software (And other illusions about testing), by Jerry Weinberg.
Six Thinking Hats, by Edward de Bono.
*In my notes I got a book called Software Test Techniques by Lee Copeland, but the only book I managed to find is this one.
** Yeah, those are not 5 books.
Subscribe to:
Posts (Atom)
Letting it go.
I dropped my Twitter account. And somehow, it did not make sense to write a tweet about it. Many years ago, when I was riding by bike as cou...
-
When I read the Context Driven Principles, and I think in the testing I do, this is how I interpret them: The value of any practice depend...
-
I just went to Brighton to meet Michael Bolton and his one day Rapid Software Testing for Managers training course, Let me tell you how this...
-
The analogy about testing being as touring some new place has been quite used. There are even books trying to coin that all Exploratory Test...