Topic: How to guarantee test coverage

Message

If you dont find a requirements document, then create one and get it documented, reviewed and get it officially established. 
This might be very important to make sure you have
a
list of things that you can test against and a set of values against
which you can compare your test results. The document need not be
complete in all respects, but as long as you have a document that
everyone accepted and signed, you atleast have a valid case for
argument if something went wrong.
(You dont want people coming back
to you saying 'how did you decide this should be the output?', This is
the way it should work... etc)

Without stated requirements you
may not be able to prove that you found a bug, and in the worst case,
all your tests may be invalidated.

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: How to guarantee test coverage Posted: 25Oct2007 at 4:23am
	If you dont find a requirements document, then create one and get it documented, reviewed and get it officially established. This might be very important to make sure you have a list of things that you can test against and a set of values against which you can compare your test results. The document need not be complete in all respects, but as long as you have a document that everyone accepted and signed, you atleast have a valid case for argument if something went wrong. (You dont want people coming back to you saying 'how did you decide this should be the output?', This is the way it should work... etc) Without stated requirements you may not be able to prove that you found a bug, and in the worst case, all your tests may be invalidated. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Functional Testing @ OneStopTesting