In Software testing, when the expected and actual behavior is not matching, an incident needs to be raised. An incident may be a Bug. It is a programmer's fault where a programmer intended to implement a certain behavior, but the code fails to correctly conform to this behavior because of incorrect implementation in coding. It is also known as Defect.
Following is the workflow of Bug Life Cycle:
The Following details should be part of a Bug:
Date of issue, author, approvals and status.
Severity and priority of the incident.
The associated test case that revealed the problem
Expected and actual results.
Identification of the test item and environment.
Description of the incident with steps to Reproduce
Status of the incident
Conclusions, recommendations and approvals.
10 Lectures 1 hours
17 Lectures 1.5 hours
60 Lectures 5 hours
99 Lectures 10 hours