Bugs which found during software testing

1. Bug: The error which founds before the products handled over to the customer.
2. Bug Reporting : The report with detailed document to show the malfunctioning or bug found out in the software to Developer.
3. Bug Tracking: To track the bugs and review it.
4. Bug Tracking System: The system which is designed to track bug and periodic review of the bug through change request.

Tips to track the bug.
1. The good tester always uses minimal steps to reproduce the bug. If the steps are minimal then it will be easy to reproduce the same by the developer.
2. IT should be like that the bug should be closed by the person who found the bug first. Anybody can solve the bug but it is only that person can make sure whether what he found out is being fixed.
3. There are methods like fixed, won’t fix, postponed, not reproducible, duplicate or by design like so many paradigms.
4. When the reproducing steps missing then programmers often make this excuse that the bug report is missing and it is not reproducible.
5. There should be a checkpoint for every version of the software that is releasing to the tester. So that they can avoid the confusion during the testing whether a bug is fixed or not fixed. If a checkpoint version control will help to track the changes that are made in the software.
6. The testers should use a bug database that the programmers can easily track. Programmers should not accept any bug other than through bug database. If a tester send mail describing a bug to the programmer is should be send back to them to put it into bug data base saying that the email can’t be tracked.
7. Tester should not mail the programmer saying about the bug instead the tester should put the bug in bug database. Database will contact the corresponding programmer through emails.
8. Programmer should make sure that his colleagues are also familiar with bug database.
9. Manager have to make assure that the bug database that he had installed is fully functioning it is using correctly.
10. Bug database should be standard. The fields of the database should not be modified again.

Priority in Bug tracking
This one is to prioritize the bugs’ importance so that they can be fixed.
The priorities are
P1 - Fix in next build
P2 - Fix as soon as possible
P3 - Fix before next release (default).
P4 - Fix if time allows
P5 - Unlikely to be fixed

Bug tracking severity
This is to mention the effect of the bug in software.
Blocker - Blocks development and/or testing work
Critical - crashes, loss of data, severe memory leak
Major - major loss of function
Normal - Minor loss of function. Unfriendly behavior that is hindering, but workable, for the user or service
Minor - Minor loss of function. Unfriendly behavior that is merely annoying to the user
Trivial - cosmetic problem like misspelled words or misaligned text
Enhancement - Request for enhancement

Bug Life Cycle
As the bug is found it goes through various stages these are the stages.
NEW: added new to assignment, analysis, fixing and reassignment.
ASSIGNED: The programmer accepts this work that they have to work on this one. Which should be analyzed, assigned and fixed.
REOPENED: Once resolved got reopened because of some new problem or for enhancement. It is new assigned and should be analyzed and should be fixed.
RESOLVED: those are which is finished the work by analyzing and fixing.
VERIFIED Quality assurance should approve this fix and put as verified.
CLOSED This one is the finished by reopening it can be reopened in some cases.

Resolutions
Fixed - The Bug is fixed
Invalid - The problem described is not a bug
WontFix - The bug will never be fixed
Later - The bug will not fixed in current version
Remind - The bug probably wont be fixed in current version but it should be reminded
Duplicate - This is a duplicate of an earlier reported problem.
Worksforme – Not reproducible.
Moved – Bug is shifted to other database.

Effective bug reporting
Keep bug reporting simple:
Only necessary data should be provided during the bug reporting.
Describe how to reproduce bugs:
Exact steps should be given to reproduce the bug
Record how bugs are detected:
Give all the avaialbe data that how the bug is appeared.
Write bug reports immediately:
Bug report should be immediately filled. If you wait that would be very hard to reproduce the steps.
Writing a one-line report summary:
A summary should be there for that for recollecting.