Normal 0 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

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 deaadlines, etc.)

- Test cases completed with certain percenttage passed

- Test budget depleted

- Coverage of code/functionality/requiremennts reaches a specified point

- Bug rate falls below a certain level

- Beta or alpha testing period ends

Very difficult to answer for this question. This is depends upon project requirements, timeline, risks, costs etc. Deciding how much testing is enough should take account of the level.of risk, including technical and business risks related to the product and projectconstraints such as time and budget