A lesson to be learned from OAT
is that the planning which assumes a test
will only run just once requires the best
environmental outcome, that there’ll be
no faults to find, and that the personnel
will be available to run as planned.
This doesn’t happen – often tests are canned,
the system breaks, or scripts aren’t running well.
Each test should be assumed to run at least
two times, with some days left aside to do
investigations, and to test the new
code fixes some before they are released.
It’s no good planning that we’ll hit a date
if known retesting means that we’ll be late.
Originally written for work, in a continuous paragraph rather than broken into lines.