In previous posts in this series, I made a claim about the audience for a test report: They almost certainly don’t want to know about when the testing is going to be done (although they might think they do). It’s true that managers frequently ask testers when the testing will be done. That’s a hard question to answer, but maybe not for reasons that you—or they—might have considered. By definition, … Read more

In the previous post in this series, I made these claims about the audience for test reports: It’s far more likely that they want an answer to these questions: What is the actual status of the product? Are there problems that threaten the value of the product? How do you—the tester—know? Do these problems threaten the on-time, successful completion of our work? In this post, I’ll address the first two … Read more

Last time, Frieda and I had been looking at visualizations of time spent on various testing activities, include work that foster test coverage of the product (T time), bug investigation and reporting (B time) and setup work to get ready to test, or tidying up afterwards (S time). “So…,” Frieda mused, “I could track T-time, and B-time, and S-time. But I’d be a little worried about watching the clock all … Read more