Google Ads

Bug Life Cycle

When QA finds any issue or bug that are responsible to report it in a systematic way. The bug life cycle continues from the very beginning to end of the bug. Tester is responsible to open and close it.
There are two type of bug:
  • Functional (i.e. Action)
  • Cosmetic (i.e. Spelling mistake)  
 
Fig: Bug life cycle.

As soon as tester finds any issue/bug they should report it to the appropriate person (i.e. Test Lead). When Test Lead confirms its a bug, tester should create/ open a bug using bug tracking tools (i.e. JIRA). Then it will be assigned to developer team. As the developer resolved the bug, it comes back to the tester/QA. Then tester again test the bug is fixed or exists. If bug is fixed then it is verified and then closed. If not fixed, tester re-open it and it goes back to the developer. Sometimes developer says it will be fixed later/near future, then it is called deferred.

Steps to report a bug:
  •  Find a valid bug
  •  Open a bug
  •  Summery/Title of a bug, Description
  •  Describe steps how to reproduce the bug.
  •  Take a snapshot, even create a video if possible.
  •  Explain Severity - How severe the bug is.
  •  Set priority - how soon it should get fixed.