I enjoy using tools to support my testing. As a former production coder, automated tests can be a refreshing respite from the relatively imponderable world of product analysis and heuristic test design (I solve sudoku puzzles for the same reason). You know, the first tests I ever wrote were automated. I didn’t even distinguish between […]

Here is my policy for accepting comments that you make on this blog:
1. I moderate all comments. I accept comments for one or more of the following reasons:
- I value a dialectic approach to learning. So I appreciate critical comments, and I will respond to them. If I don’t write a specific response, that means […]

Now for a word about testing companies.
I’ve worked at two testing companies, not counting my own. I’ve toured several others, and I know which ones have a standing among the people who themselves have a public reputation in the testing field. Occasionally I am approached for an endorsement. I’m happy to give endorsements, but only […]

Sometimes, you can improve your thinking just by avoiding using certain terms. I stopped using “best practice”, years ago. When I am tempted to use the term in a serious discussion of methodology, I am forced to use an alternative, and that alternative is always superior.
It’s just like giving up the use of the goto […]

When a programmer builds a product, should he release it to the testers right away? Or should he test it himself to make sure that it is free of obvious bugs?

Many testers would advise the programmer to test the product himself, first. I have a different answer. My answer is: send me the product the […]