Topic: Testing FAQ

Message

   How can it be known when to stop testing?

This can be difficult to determine. Many modern software applications
are so complex, and run in such an interdependent environment, that
complete testing can never be done. Common factors in deciding when to
stop are:

    * Deadlines (release deadlines, testing deadlines, etc.)

    * Test cases completed with certain percentage passed

    * Test budget depleted

    * Coverage of code/functionality/requirements reaches a specified point

    * Bug rate falls below a certain level

    * Beta or alpha testing period ends 

 What if there isn't enough time for thorough testing?

		Use risk analysis to determine where testing should be focused.

Since
it's rarely possible to test every possible aspect of an application,
every possible combination of events, every dependency, or everything
that could go wrong, risk analysis is appropriate to most software
development projects. This requires judgement skills, common sense, and
experience. (If warranted, formal methods are also available.)
Considerations can include:

    * Which functionality is most important to the project's intended purpose?

    * Which functionality is most visible to the user?

    * Which functionality has the largest safety impact?

    * Which functionality has the largest financial impact on users?

    * Which aspects of the application are most important to the customer?

    * Which aspects of the application can be tested early in the development cycle?

    * Which parts of the code are most complex, and thus most subject to errors?

    * Which parts of the application were developed in rush or panic mode?

    * Which aspects of similar/related previous projects caused problems?

    * Which aspects of similar/related previous projects had large maintenance expenses?

    * Which parts of the requirements and design are unclear or poorly thought out?

    * What do the developers think are the highest-risk aspects of the application?

    * What kinds of problems would cause the worst publicity?

    * What kinds of problems would cause the most customer service complaints?

    * What kinds of tests could easily cover multiple functionalities?

    * Which tests will have the best high-risk-coverage to time-required ratio?

click here for more details:

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

Author	Message
appurva Newbie Joined: 09Apr2007 Online Status: Offline Posts: 1	Topic: Testing FAQ Posted: 09Apr2007 at 9:42pm
	How can it be known when to stop testing? This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: * Deadlines (release deadlines, testing deadlines, etc.) * Test cases completed with certain percentage passed * Test budget depleted * Coverage of code/functionality/requirements reaches a specified point * Bug rate falls below a certain level * Beta or alpha testing period ends What if there isn't enough time for thorough testing? Use risk analysis to determine where testing should be focused. Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include: * Which functionality is most important to the project's intended purpose? * Which functionality is most visible to the user? * Which functionality has the largest safety impact? * Which functionality has the largest financial impact on users? * Which aspects of the application are most important to the customer? * Which aspects of the application can be tested early in the development cycle? * Which parts of the code are most complex, and thus most subject to errors? * Which parts of the application were developed in rush or panic mode? * Which aspects of similar/related previous projects caused problems? * Which aspects of similar/related previous projects had large maintenance expenses? * Which parts of the requirements and design are unclear or poorly thought out? * What do the developers think are the highest-risk aspects of the application? * What kinds of problems would cause the worst publicity? * What kinds of problems would cause the most customer service complaints? * What kinds of tests could easily cover multiple functionalities? * Which tests will have the best high-risk-coverage to time-required ratio? click here for more details: http://www.onestopfaqs.com/faqs/1617/ Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


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