Topic: Testinfg FAQ

Message

   What if the project isn't big enough to justify extensive testing?

		Consider the impact of

project errors, not the size of the project. However, if extensive testing is

still not justified, risk analysis is again needed and the same considerations

as described previously in 'What if there isn't enough time

for thorough testing?' apply. The tester might then do ad hoc testing, or

write up a limited test plan based on the risk analysis

What if the software is so buggy it can't really be tested at all?

The best bet in this situation is for the testers to go through the
process of reporting whatever bugs or blocking-type problems initially
show up, with the focus being on critical bugs. Since this type of
problem can severely affect schedules, and indicates deeper problems in
the software development process (such as insufficient unit testing or
insufficient integration testing, poor design, improper build or
release procedures, etc.) managers should be notified, and provided
with some documentation as evidence of the problem.

click here for more details:

http://www.onestopfaqs.com/faqs/1615/

Author	Message
appurva Newbie Joined: 09Apr2007 Online Status: Offline Posts: 1	Topic: Testinfg FAQ Posted: 09Apr2007 at 9:28pm
	What if the project isn't big enough to justify extensive testing? Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the same considerations as described previously in 'What if there isn't enough time for thorough testing?' apply. The tester might then do ad hoc testing, or write up a limited test plan based on the risk analysis What if the software is so buggy it can't really be tested at all? The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem. click here for more details: http://www.onestopfaqs.com/faqs/1615/ Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged

praveen.1781 Newbie Joined: 29Oct2007 Online Status: Offline Posts: 1	Posted: 31Oct2007 at 3:22am
	What if the software is so buggy it can't really be tested at all? In this situation the best bet is to have test engineers go through the process of reporting whatever bugs or problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules and indicates deeper problems in the software development process, such as insufficient unit testing, insufficient integration testing, poor design, improper build or release procedures, managers should be notified and provided with some documentation as evidence of the problem.
	IP Logged


One Stop Testing Forum : Quality Assurance @ OneStopTesting : Defect Management@ OneStopTesting