A lesson to be learned from OAT
\nis that the planning which assumes a test
\nwill only run just once requires the best
\nenvironmental outcome, that there’ll be
\nno faults to find, and that the personnel
\nwill be available to run as planned.
\nThis doesn’t happen – often tests are canned,
\nthe system breaks, or scripts aren’t running well.
\nEach test should be assumed to run at least
\ntwo times, with some days left aside to do
\ninvestigations, and to test the new
\ncode fixes some before they are released.
\nIt’s no good planning that we’ll hit a date
\nif known retesting means that we’ll be late.<\/p>\n
Originally written for work, in a continuous paragraph rather than broken into lines.<\/p>\n","protected":false},"excerpt":{"rendered":"
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 … Continue reading OAT Completion Report: Secret Sonnet<\/span>