The bug needs to be communicated and assigned to developers that can fix it.
After the problem is resolved, fixes should be re-testing and determinations made regarding requirements for regression testing to check that fixes didn’t create problems elsewhere.
The following are the items to consider in the tracking process:
> Complete information such that developers can understand the bug, get an idea of its severity, and reproduce it if necessary.
> Bug identifier (number,ID),etc.
> Current bug status.(e.g, ‘open’,’closed’, etc)
> The application name and version.
> The function, module ,feature, object, screen, etc. he bug occurred.
> Environment specifics, system, platform, hardware specifics.
> Test case name/number/identifier.
> Severity level.
> Tester name
> Bug reporting date.
> Name of developer/group/organization the problem is assigned to.
> Description of fix.
> Date of fix.
> Application version that contains the fix.
> Verification details.
A reporting or tracking process should enable notification of appropriate personnel at various stages.
