Q: How do you know when to stop testing?
A: 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, e.g. release deadlines, testing deadlines;
- Test cases completed with certain percentage passed;
- Test budget has been depleted;
- Coverage of code, functionality, or requirements reaches a specified point;
- Bug rate falls below a certain level; or
- Beta or alpha testing period ends.
Q: What if the application has functionality that isn't in the requirements?
A: It may take serious effort to determine if an application has significant unexpected or hidden functionality, which it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer.
[Continued on next page...]
Click on a link!
Tell a friend!
______________________________________________________
Copyright 1998 - 2008 by Rob Davis PE. All rights are reserved. No part of
this document may be reproduced in any form whatsoever
without written permission from Rob Davis, PE.
http://www.softwaretestengineer.com
http://www.robdavispe.com
