[Spoorthi]

WHAT SHOULD BE DONE AFTER A BUG IS FOUND?
the bug needs to be communicated and assigned to developers that can fix it.After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didnt create problems elsewhere.If a problem-tracking system is in place,it should encapsulate these processes. A variety of commericial problem-tracking/management software tools are available. The following are items to consider in the tracking process;

• • complete information such that developers can understand the bug, get an idea of its severity,and reproduce if it necessary.
    bug identifier(number,id,etc)
    current bug status (ex:'released for retest', 'new', etc)
    the application name or identifier and version.
    the function,module,feature,object,screen, etc.where the bug occured.
    environment specifies, system, platform, relevant hardware specifics.
    test case name/number/idenfier
    one-line bug description
    full bug description.
    description of steps needed to reproduce the bug if not covered by a test case or if the developer doesnot have easy access to the test case/test script/test tool.
    what do the developers think are the higest-risk aspects of the application?
    what kinds of problems would cause the worst publicity?
    what kinds of problems would cause the most customer service complaints?
    what kind of tests could easily cover multiple functionalities?
    which tests will have the best high-risk-coverage to time-required ratio?

[au123]

Hi Spoorthi,

Nicely explained, Thanks !