The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester, which aims to provide responses to common questions and statements about testing from a context-driven perspective.
It's being edited by Lee Hawkins who is posing questions on Twitter, LinkedIn, Slack, and the AST mailing list and then collating the replies, focusing on practice over theory.
I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be.Perhaps you'd like to join me?
--00--
"What is the best testing metric?"
Now there's a question that has occupied many minds for many long hours. Don't worry, though, because this will be a short answer.
We've spoken recently about "best" and you'll recall that I said:
For me, there are real, practical, benefits to taking the perspective that there are no best practices.
It works for metrics too, on the basis that the rosette of bestness can only be awarded in context (best for who? best for what purpose? best on what basis?) and in comparison to all competitors.
But let's stable my hobby horse and answer your question. I'll assume that you want something representing the value of the testing being done rather than an indication of product or project status as an outcome of testing.
If you forced me to choose something, I think that a generally good metric for your need, if it can be collected in good faith, is this:
The extent to which the people who matter are satisfied with what they're getting from the testing, given what it costs.
That's what's important about testing.
One note: please don't read that as stakeholders know best. Part of the value testing can bring is helping people to shape what they know about what they need to know at the time they need to know it.
Image: depositphotos
Comments
Post a Comment