Today, someone on Twitter pointed to an interesting blog post by Alan Page of Microsoft. He says: “How do testers determine if a bug is a bug anyone would care about vs. a bug that directly impacts quality (or the customers perception of quality)? (or something in between?) Of course, testers should report anything that may annoy a user, but learning to differentiate between an ‘it could be better’ bug … Read more
Let’s imagine, for a second, that you had a political problem at work. Your CEO has promised his wife that their feckless son Ambrose, having flunked his university entrance exams, will be given a job at your firm this fall. Company policy is strict: in order to prevent charges of nepotism, anyone holding a job must be qualified for it. You know, from having met him at last year’s Christmas … Read more
A colleague wrote to me recently and asked about a problem that he’s had in hiring. He says… The kind of test engineers we’re looking for are ones that can think their way around a system and look for all the ways that things can go wrong (pretty standard, so far), and then code up a tool or system that can automatically verify that those things haven’t gone wrong (a … Read more
I have four or five blog posts in the hopper, each almost ready to go. I’m working on a whole book and a chapter of another one, and I’m on a deadline that I’m about to blow. The kids are still out of school, and I really should be cooking dinner right now. And yet… As I write, one of the best testers that I know is looking for work. … Read more
In a recent blog post, James Bach discusses the essence of heuristics. A heuristic is a fallible method for solving a problem or making a decision. When used as an adjective, “heuristic” means fallible and conducive to learning. James ends the post by introducing a number of questions in order to test whether someone is teaching you a heuristic effectively. Meeta Prakash, in the comments, remarks “Your questions sound so … Read more
Part of the joy of producing this blog is in seeing what happens when other people pick up the ideas and run with them. That happened when I posted a scenario on management mistakes a few weeks ago, and Markus Gärtner responded with far more energy and thought than I would have expected. Thanks, Markus. Last week I posted a transcript of a transpection session between me and James Bach. … Read more
On April 19, 2010, I was interviewed by Gil Broza. In preparation for that interview, we solicited questions from the listeners, and I promised to answer them either in the interview or in my blog. Here’s the first one. How to deal with un-experienced testers? is there a test approach that suits better for them? Here’s what I’d do: I’d train them. I’d pair them up with more experienced testers … Read more
The other day on Twitter, Cory Foy tweeted a challenge: “Having a QA department is a sign of incompetency in your Development department. Discuss.” Here’s what I think: I’m a tester, and it’s time for our craft to grow up. Whatever the organizational structure of our development shops, it’s time for us testers to get out of the Quality Assurance business. In the fall of 2008, I was at the … Read more
In the interview with the Coding QA guys that was the subject of my last post, James Bach refers exploratory testing as parallel learning test design, test execution and learning, and said that exploratory approaches are epitomized by loops. Where do loops happen in exploratory testing? In fact, exploratory testing includes both looping and branching. When we’re testing in an exploratory way, we may branch away from the current path … Read more
Several months back, James Bach did an interview with the CodingQA guys, Matthew Osborn and Federico Silva Armas. In the interview, James talks about the skills of exploratory testing, sex education (now do I have your attention?) and how to use session-based test management with minimal overhead and maximum credibility. I’m surprised at how few people have heard about the podcast, so I’m drawing attention to it here. It runs … Read more