R. Clayton (rclayton@monmouth.edu)
Tue, 28 Mar 2000 16:04:17 -0500 (EST)
What do you mean by Risks and Contingencies?
A risk is anything that could occur that would prevent you from carrying out
your testing as described by your test plan. Risks can be literally anything
from acts o' nature (flood, fire, earthquake) to acts o' man (your lead
implementer and your lead tester elope and run away to Pago Pago, your
company's stock looses six billion dollars in one day) to mundane project
matters (the code delivery date has slipped by at least two months, the support
staff has installed Windows 2000 everywhere over the weekend).
A contingency is what you plan to do to recover from a risk that has actually
occurred.
Although it's always useful to think in terms of risk and contingency, I
wouldn't worry too much about them for testing because we're going to go over
them in greater detail in the next section on management.
Is it possible to go beyond functional testing and is it required to go
beyond functional if we feel that the testing is complete with functional?
I'd like you to do both a functional test and a structural test just to have
the experience of wrestling with them. I'd also like to have you do a system
test and a unit test to get a feel for the issues involved there. Given those
requirements, it makes the most sense, to me, to do a structural unit test and
a functional system test, but I'll leave the actual details up to you.
This archive was generated by hypermail 2.0b3 on Thu Mar 30 2000 - 20:50:05 EST