What will be done after a defect/bug is found in project/application?

The bug has to be communicated and assigned to developers which will fix it.

when the matter is resolved, fixes ought to be re-tested, and determinations created concerning needs for regression testing to examine that fixes did not produce issues elsewhere.

If a problem-tracking system is in repository, it ought to encapsulate these processes.

A range of business problem-tracking/management software system tools square measure offered (see the 'Tools' section for net resources with listings of such tools).

the subsequent square measure things to contemplate within the chase process:

•         Complete info specified developers will perceive the bug, get a plan of its severity, and reproduce it if necessary.

•         Bug symbol (number, ID, etc.)

•         Current bug standing (e.g., 'Released for Retest', 'New', etc.)

•         The application name or symbol and version

•         The perform, module, feature, object, screen, etc. wherever the bug occurred

•         Environment specifics, system, platform, relevant hardware specifics

•         Test case name/number/identifier

•         One-line bug description

•         Full bug description

•         Description of steps required to breed the bug if not coated by an action or if the developer does not have quick access to the check case/test script/test tool

•         Names and/or descriptions of file/data/messages/etc. utilized in check

•         File excerpts/error messages/log file excerpts/screenshots/test tool logs that may be useful to find the explanation for the matter

•         Severity estimate (a 5-level vary like 1-5 or 'critical'-to-'low' is common)

•         Was the bug reproducible?

•         Tester name

•         Test date

•         Bug reportage date

•         Name of developer/group/organization the matter is assigned to

•         Description of downside cause

•         Description of fix

•         Code section/file/module/class/method that was fixed

•         Date of fix

•         Application version that contains the fix

•         Tester responsible for retest

•         Retest date

•         Retest results

•         Regression testing requirements

•         Tester responsible for regression tests

•         Regression testing results

•         A reporting or tracking process should enable notification of appropriate personnel at various stages.

•         For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers.