Every tester finds bugs, but a bug is only useful if it is reported and tracked well. The bug life cycle shows the steps a bug goes through, from the moment you find it to the moment it is closed. It is also a favourite topic in testing interviews. At Asmorix Technologies, a Software Training Institute in Chennai, learners practise reporting bugs on real-style applications.
New
You find a problem and log it in a tracking tool, such as Jira. A good report includes a clear title, the steps to repeat it, the expected result, the actual result, and a screenshot.
Assigned
A lead reviews the bug and assigns it to a developer. If the bug is unclear, it may be sent back to you for more details.
Open
The developer starts to study the problem and works on a fix.
Fixed
Once the developer changes the code, the bug is marked as fixed and sent back for testing.
Retest
You run the same steps again to check whether the problem is gone. This step needs care, because a fix can sometimes break something else.
Verified and Closed
If the problem no longer appears, you mark the bug as closed. If it still appears, you reopen it with a note about what you saw.
Other Statuses
A bug may also be marked as rejected, duplicate, deferred, or not a bug. Know what each one means, since interviewers often ask.
Severity and Priority
Severity shows how serious the effect is, and priority shows how soon it should be fixed. Both appear in every good bug report.
Practise Writing Reports
Find a small issue on a practice website and write a full report for it. Ask a friend to follow your steps.
Build Your Testing Skills
Visit Asmorix Technologies to view the software testing syllabus and choose a batch that suits you.
Top comments (0)