What is the difference between bug tracking and bug reporting?
What is meant by bug life cycle?
Who decide the priority? It is an interview question
Printable View
What is the difference between bug tracking and bug reporting?
What is meant by bug life cycle?
Who decide the priority? It is an interview question
Bug tracking is to finding the bug, retesting it and confirming that the bug is reproduce able .
Bug reporting is to making a report about the bug, it's severity and priority and sending this report to respective person(developer/ of bug reporting tool).
Bug life cycle tell about when bug occur, what is the status of the bug, it's ixed or not.Means , journey of bug status from "new" bug to "fixed/rejected" status is bug life cycle.
Priority is decided by CCB, but generally it's the tester who decide it.
Hi Sakshi,
We can log a bug into Bug tracking tool where we need to provide all the information of a bug like Description, Steps to produce the bug, priority, severity, build number, Date... Unique Bug id will be generated automatically and same information we give in excel sheet if we don't have tool and in this we have to give the Unique bug id. This is nothing but bug reporting.
After reporting the bug, that'll be fixed by developer and he change the status like resolved fixed.....after that we have to reverify the bug. If we don't have any tracking system(bug tracking tool), then that'ld be really kill our time. Now-a-days everybody using Bug tracking tool like Test Director, Bugilla........So when we log the bug automatically one bug id will be created. When we want to see the bug we can search the bug by entering the status as resolved. then all the resolved bugs will come as a list. then u can open the bug and verify and u have to reopen or u can close it. like this Tracking the bug goes on.
Bug life cycles is nothing but the process the bug from state to state.
1. We log a bug and it's status is new.
2. After that developer accept that and he'll change the status to Active/New.
3. After that he'll fix the bug and he'll change the status to Resolved/fixed.
4. After that tester (we) verify the bug on the latest build and we'll close the bug if that is really fixed otherwise we'll reopen the bug and we'll mention the latest build number. Like this the process goes on.
5. We have somany statuses like won't fix, as per design, document bug......etc
coming Your last question, Severity and priority will be given in bug report when we log the bug.
Severity is nothing but the impact of the bug with respect to functionality.
Priority is impact of the bug with respect to Client Requirements.
Generally, it changes from company to company, In some companies priority will be defined by TL or PL and in some other tester will set priority.