Tactical testing is the incorporation of testing code into the working source code, so it is WhiteBoxTesting made extreme. I have heard about DesignForTestability, and we all know that TheSourceCodeIsTheDesign, so it follows that we should code for testability. As that's clearly a low-level operation, I call it TacticalTesting.
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:
These ideas are called:
Contributors: JohnFarrell
See also: CategoryTesting TacticalTestingFramework