Yesterday, Nestor Arellano from ITWorld Canada, an online publication, called me and sent an email, seeking comment on a press release about the Top 25 Programming Errors. I glanced at the list of errors that he had sent me, and it seemed to me that they had missed the most important programming error of all: failing to ask if the program does something useful or valuable, and failing to consider … Read more
At the Software Testing Club, Phil Kirkham asked a question headed “What Colour Tester Are You?” Another totally unscientific survey – how many readers of this site would consider themselves to be black box testers, white box testers or grey box testers ? Or if you are a test manager, what colour testing do the testers you are in charge of do? I whimsically replied, “I deny the existence of … Read more
The problem reported in this post has been, uh, fixed. Check the right-hand edge of the image.
If you want to understand what context-driven testing is all about, James Bach and Cem Kaner have recently collaborated on a statement of what it is, and a lengthy explication. It’s posted on Cem Kaner’s blog at http://www.satisfice.com/kaner. The posting covers the territory admirably, and I wholeheartedly agree with it. In particular, the statement emphasizes that adaptation to the needs of the project is the first step in the context-driven … Read more
Apparently. Please don’t misunderstand. I love the principles in the Agile Manifesto (including Robert Martin’s proposal for the fifth, “Craftsmanship over crap.”) I have great enthusiasm and respect for those who have advocated the role of testing in Agile projects. But in order to push these ideas forward, let’s make sure to test our stuff, to make sure that it doesn’t accidentally bring discredit to the ideas.
In response to this posting, Clive asks, “So in your opinion what should a test plan contain?” First, Clive, thank you for asking. Let’s consider first what we might mean by “plan”. The way James Bach and I talk about planning (and the way we teach it the Rapid Software Testing course) is that a plan is the sum or intersection of strategy and logistics. Strategy is the set of … Read more
Testing, in the quick definition that James Bach and I use, is questioning a product in order to evaluate it. One way of questioning the product is to ask ordinary questions about it, and then to operate it—supplying it with input of some kind, and operating it in some way. The product “answers” us by producing output or otherwise exhibiting behaviour, which we observe and evaluate. Another way of questioning … Read more
I’m off to Vancouver, British Columbia, teaching Rapid Software Testing to a corporate client the week of December 8. Live near there? Want to get together and chat about testing? I’ll be there Monday through Friday nights. Drop a line to me at mb@michaelbolton.net.
I’m ambivalent about honours. Recognition is nice, but I’m skeptical about the notion of winning over other worthy nominees. Nonetheless, at the EuroSTAR conference, I accepted the inaugural EuroSTAR 2008 CapGemini Award for Innovation, recognizing the most innovative track session, for my talk Two Futures of Software Testing. We won! Who won? Well, I did for the presentation itself, but James Bach, Cem Kaner, and Jerry Weinberg share credit for … Read more
Galvanized by Jerry Weinberg‘s workshop on experiential learning at AYE 2008, I led a tutorial at EuroSTAR 2008 that included an experiential exercise invented by my colleague James Bach. I call it The Heuristics Art Show. In small groups, people contributed, discussed, and refined headlines and descriptions of some of their heuristics, mostly to do with testing, but also to do with other aspects of life and software development. It … Read more