Very Short Blog Posts (28): Users vs. Use Cases

Thursday, May 07, 2015 17:26 PM

As a tester, you’ve probably seen use cases, and they’ve probably informed some of the choices you make about how to test your product or service. (Maybe you’ve based test cases on use cases. I don’t find test cases a very helpful way of framing testing work, but that’s a topic for another post—or for […]

Very Short Blog Posts (27): Saving Time

Wednesday, April 29, 2015 19:41 PM

Instead of studying and learning from every bug, you can save a lot of time by counting and aggregating bug reports. That’s a good thing in its way, because if you don’t study and learn from every bug, you’ll need all the time you can get to deal with problems that seem to keep happening […]

Exploratory Testing 3.0

Tuesday, March 17, 2015 04:09 AM

This blog post was co-authored by James Bach and me. In the unlikely event that you don’t already read James’ blog, I recommend you go there now. The summary is that we are beginning the process of deprecating the term “exploratory testing”, and replacing it with, simply, “testing”. We’re happy to receive replies either here […]

Oracles Are About Problems, Not Correctness

Friday, March 13, 2015 02:49 AM

As James Bach and I have have been refining our ideas of testing, we’ve been refining our ideas about oracles. In a recent post, I referred to this passage: Program testing involves the execution of a program over sample test data followed by analysis of the output. Different kinds of test output can be generated. […]

Very Short Blog Posts (26): You Don’t Need Acceptance Criteria to Test

Tuesday, February 24, 2015 20:08 PM

You do not need acceptance criteria to test. Reporters do not need acceptance criteria to investigate and report stories; scientists do not need acceptance criteria to study and learn about things; and you do not need acceptance criteria to explore something, to experiment with it, to learn about it, or to provide a description of […]

Very Short Blog Posts (25): Testers Don’t Break the Software

Wednesday, February 18, 2015 04:28 AM

Plenty of testers claim that they break the software. They don’t really do that, of course. Software doesn’t break; it simply does what it has been designed and coded to do, for better or for worse. Testers investigate systems, looking at what the system does; discovering and reporting on where and how the software is […]

Give Us Back Our Testing

Sunday, February 15, 2015 00:47 AM

“Program testing involves the execution of a program over sample test data followed by analysis of the output. Different kinds of test output can be generated. It may consist of final values of program output variables or of intermediate traces of selected variables. It may also consist of timing information, as in real time systems. […]

Very Short Blog Posts (24): You Are Not a Bureaucrat

Saturday, February 07, 2015 21:38 PM

Here’s a pattern I see fairly often at the end of bug reports: Expected: “Total” field should update and display correct result. Actual: “Total” field updates and displays incorrect result. Come on. When you write a report like that, can you blame people for thinking you’re a little slow? Or that you’re a bureaucrat, and […]

The Rapid Software Testing Namespace

Monday, February 02, 2015 08:42 AM

Just as no one has the right to tell you what language to speak at home, nobody outside of your project has the authority to tell you how to speak inside your project. Every project develops its own namespace, so to speak, and its own formal or informal criteria for naming things inside it. Rapid […]

Very Short Blog Posts (23) – No Certification? No Problem!

Wednesday, January 28, 2015 08:14 AM

Another testing meetup, and another remark from a tester that hiring managers and recruiters won’t call her for an interview unless she has an ISEB or ISTQB certification. “They filter résumés based on whether you have the certification!” Actually, people probably go to even less effort than that; they more likely get a machine to […]