Instead of asking “What tests should I automate?" consider asking "What specific fact do I want to check? What’s a really good way to check that fact? Is that the fastest, earliest, easiest, least expensive way to check it? Do I really need to check this fact? Is it worth it?"
"What risk am I addressing by checking this fact? Is it a serious risk? Why do we think it is? Is that foreboding feeling trying to tell us something?
"What problems, near here or far away, might I be missing as a consequence of focusing on this fact, and checking it this way?"
"What problems, near here or far away, might I be missing as a consequence of focusing on this fact, and checking it this way?"
"Do I know enough about the product, and where there might be problems, to be sure that this fact really is the most valuable thing to check? What would cause this fact to change? Is that likely? Am I the right person to take responsibility for checking it? The only person?"
For each fact you're thinking about checking, consider those questions.
"But that will take a long time!", you might reply.
Not that long. Compare it with how long it takes to develop and run and interpret and revise and review and maintain even one worthless check.
"But that will take a long time!", you might reply.
Not that long. Compare it with how long it takes to develop and run and interpret and revise and review and maintain even one worthless check.
Now it’s true, you can save some time and effort in that process by not interpreting and reviewing and maintaining the checks. That is, essentially, ignoring them. But if you’re not going to pay attention to them, why bother with them at all? Plus they might lull you to sleep.
With practice, the questions that I offered above can be asked routinely far more quickly than automating even one check. Ask your own questions too. If you pay attention to the answers, you can be more sure that every check is powerful, valuable, and inexpensive.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
