You are on page 1of 2


1. Testing Team (TT) receives the patch from Change Control Administrator (CCA) via
2. The application is installed and testing begins.
3. Each TT member enters the bugs found in a Bug Report.
4. The Senior Resource (SR) mails the Bug Report to the entire Development Team
(DV), a copy to the Development Manager (DM), TT and the Product Manager (PM).
5. The TT receives the bug fixes sent by the DV at pre-defined intervals.
(The TT along with the DV decides about the interval of bug fixes, which may vary from once
a day to three times a day).
6. The TT installs the newly received patch.
7. The TT verifies the reported bugs and updates the status accordingly.
(If the bug is not fixed then the DV is informed through email and bug status is set to ‘A’).
8. At the end of the day, a consolidated Bug Report with updated bug statuses will be
sent by the TT to the DM and PM, and a copy to DV and TT.
9. Testing ends when the exit criteria are met.
(Exit criteria would be decided upon on the basis of time and functionality tested).
10. At the end of testing, SR notifies the entire team about the completion of testing
through a mail sent to DV, TT and a copy to DM and PM.
11. The latest installs at the TT end along with a consolidated Bug Report for the entire
Cycle will be sent to the CCA and a copy sent to the DM, PM, DV and TT.
Pros and Cons

 Bug fixing is going on in parallel with Bug reporting which results in a product with
bugs not only identified but also fixed at the end of the testing effort. This implies an
improved product quality.
 Localized Regression can be made possible with this approach. Bug fixes are being
verified with in lesser time and if any bug has an impact on the respective
functionality the impact will be identified readily.
 The entire team along with the managers is informed daily about the testing status
thereby being aware of the number of bugs being fixed and the bugs which need to be
 Apparently this might reflect an increase in the time required but effectively this is
reducing the time by a large proportion:
o Since bug fixing is in parallel with testing the DV does not need additional
cycle for bug fixing. The second cycle that follows would primarily be a
testing effort and may be started after end of first cycle serving the purpose of
application regression testing within a reduced time frame.

 The TT will have to install the product several times and this might require effort and