Tactical testing is the incorporation of testing code into the working source code, so it is
made extreme. I have heard about
, and we all know that
, so it follows that we should code for testability. As that's clearly a low-level operation, I call it
Is this going to become a
PatternLanguage for testing?
It could one day become a
PatternLanguage for WhiteBoxTesting, but I am not so sure how much I believe in WhiteBoxTesting, nor how much time I have to do it.
The things you want to achieve from tactical testing are:
test all the paths in the program
test unusual boundary conditions
test unusual data sets
allow RegressionTesting to be done by people other than the developers, and preferably with an automated TestingFramework
[please add more here]
It seems to me that tactical testing has to be language specific.
The code is language specific (!) and that's what we're interested in
As testing Java programs is my current problem, I will write about the
ideas I have had for that.
These ideas are called:
There is some disagreement about:
Techniques that are not tactical testing include:
of this page
(last edited EditText February 16, 2005)
or FindPage with title or text search