Defect tracking process and Bug Life Cycle – Manual Testing Training

 

Defect tracking process and Bug Life Cycle – Manual Testing Training

 

h)  Defect tracking process :

 

i)  Test case related defect fixing :

j)  Test data related defect fixing :

k)   Test environment related defect fixing  :

     l)  Coding related defect or bug fixing:

From the above process developers can place modified sprint with new version number in soft base folder in server computer.

Developers can send an email to testers by specifying details of

i) Enhancements and new features,

ii) Bug fixes and

iii)  Known bugs and limitations.

By reading “SRN” email tester can concentrate on new test cycle.

 

Example:

 

From the above example, testers can receive modified sprint build after fixing bugs by developers.

 

Tester can study “SRN” document given by developers to understand how bugs are fixed by developers and then related testers can conduct smoke testing by executing a fixed set of cases to confirm the modified sprint is working or not.

 

After smoke testing related testers can execute previously failed cases on modified sprint. If they are passed then testers can go to sanity testing and regression testing. If they are failed once again then testers can report defect as reopen.

 

If retesting was passed then related testers can go to execute previously passed cases on modified sprint, which cases are most related to previously failed cases. If Sanity testing was passed then testers will go to regression testing, otherwise the testers can report defect as new.

 

If sanity testing was passed then related testers can got o regular regression testing by executing previously passed cases on modified sprint, which cases are related to previously failed case. If regression testing was passed, then related testers can go to further real testing. If regression testing was failed testers can report defect as new.

 

 

m) Bug Life Cycle (BLC):

 

 

From the above bug life cycle, we can get below sub cycles:

 

New   —->  Deferred

New    —–>  Open  —-> Fixed —-> Closed

New  —-> Reject  —> Closed

 

 

 

 

 

 

 

 

n)   Test cycle vs Bug age:

 

Test cycle means the time gap in between to consecutive sprint releases from developers.

Bug age means the time gap in between defect reporting to developers and bug closing via retesting, sanity testing, regression test.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In this article we have seen Defect tracking process and Bug Life Cycle – Manual Testing Training .In the next article will see Test Closure.