Hi Raju, There are many ways to state/prove a build is in a stable state. First, it need to be established and agreed upon in the test plan. There should be an entrance/exit criteria that specifically states the percentage of tests that need to passed before accepting the system in the next phase of testing. So assuming you are a system tester, then you should have an exit criteria from Unit Testing. Usually, this is a pass percentage above 90% with no major defects. The next thing you should have is a shakeout test/smoke tests. These test are designed to verify the major functionality is working and no issues are found that impact your system test cases. If the entrance/exit criteria are met and the shakeout/smoke tests are successful, then you can be confident you have a build in a stable state.
Hopes this helps. On Monday, September 3, 2012 12:54:06 AM UTC-4, Raju Tester wrote: > > Hi Friends, > > This is Raju. Can any one clears my doubt? How can a Tester say that the > Build is in Stable State? > > Regards > RAJU > -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en
