|
Knowing when to put testing to a hold or stop it completely can be hard to define. Many of the today’s highly complex applications are so large and interdependent over other systems, that testing can never be completed. However, usually the common aspects to suggest stopping the testing process include the following:
• Deadlines, these may be release deadlines i.e. when the project is to be released, or the testing deadlines etc. • A certain percentage of test cases completed and passed • The testing budget has been completely consumed • Treatment of the functionality/requirements/specifications/code has reached a specified point • The occurrence of bug is reduced to a certain level • The alpha and beta testing period has completed |
| Sponsored Links: |
| << back |