DevelopsenseLogo

More of What Testers Find

Damn that James Bach, for publishing his ideas before I had a chance to publish his ideas! Now I’ll have to do even more work! A couple of weeks back, James introduced a few ideas to me about things that testers find in addition to bugs.  He enumerated issues, artifacts, and curios.  The other day I was delighted to find an elaboration of these ideas (to which he added risks … Read more

Why Do Some Testers Find The Critical Problems?

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

One Test Per Requirement

Despite all of the dragons that Agile approaches have attacked successfully, a few still live. As crazy as it is, the idea of one test check per requirement has managed to survive in some quarters. Let’s put aside the fact that neither tests nor requirements are valid units of measurement, and focus on this: If you believe that there should be one test per requirement, then you have to assume … Read more

Exegesis Saves (Part 3) Beyond the Bromides

Over the last few blog posts, some colleagues and I have been analyzing this sentence: “In successful agile development teams, every team member takes responsibility for quality.” Now, in one sense, it’s unfair for me to pick on this sentence, because I’ve taken it out of context. It’s not unique, though; a quick search on Google reveals lots of similar sentences: “Agile teams work in a more collaborative and open … Read more

Exegesis Saves! (Part 2) Transpection with James Bach

Last evening, after a long session of collecting and organizing a large number of contributed responses to yesterday’s testing challenge, I was going over my own perspectives on the sentence “In successful agile development teams, every team member takes responsibility for quality.” James Bach appeared on Skype, and we began an impromptu transpection session. It went more or less like this: James: I saw your original challenge and a couple … Read more

Exegesis Saves! (Part 1)

This morning, I read a sentence that bugged me. “In successful agile development teams, every team member takes responsibility for quality.” I’ve seen sentences of that general form plenty of times before. Whether I’ve reacted or not, they’ve always bugged me, and today I decided to probe into why. Rather than doing so on my own, I thought it would be more fun and more interesting to involve my community, … Read more

EuroSTAR Trip Report, Part 2

In this post, I’ll highlight a few more of the people that I met at EuroSTAR 2010. Please note that because there were so many people that I’d like to mention, there’s still more to come in subsequent posts. Also, I’ve included tons of links to these people and their work. Please use those links! Shmuel Gershon (@sgershon on Twitter) was in the Test Lab a lot, only one of … Read more

EuroSTAR Trip Report, Part 1

Way way back in 2003, Bret Pettichord first published a paper on schools of software testing. The paper was controversial. Some people found it helpful to identify different schools of thought, for the purpose of understanding ways in which reasonable people might disagree reasonably.  Others found even the mention of disagreements within the field to be distasteful and divisive.  Some people identified with particular schools. Others, sometimes indignantly, refused to … Read more

Context-Free Questions for Testing

In Jerry Weinberg and Don Gause’s Exploring Requirements, there’s a set of context-free questions to ask about a product or service. The authors call them context-free questions, but to me, many of them are more like context-revealing questions. In the Rapid Software Testing class, the participants and the instructors make discoveries courtesy of our exercises and conversations. Here’s a list of questions that come up fairly consistently, or that we … Read more

Project Estimation and Black Swans (Part 5): Test Estimation

In this series of blog posts, I’ve been talking about project estimation. But I’m a tester, and if you’re reading this blog, presumably you’re a tester too, or at least you’re interested in testing. So, all this has might have been interesting for project estimation in general, but what are the implications for test project estimation? Let’s start with the tester’s approach: question the question. Is there ever such a … Read more