This tutorial describes what a "software defect" (also know as software bug , incident , fault) is and explains how to report one.
Please be patient . Video will load in some time. If you still face issue viewing video click here
Video Transcript with Key Takeaways Highlighted:
While executing test cases you may find that actual results vary from the expected results. This is nothing but a defect also called incident , bug , problem or issues.
In case you find a defect , What information would you convey to a developer to help him understand the defect ? Pause the training and think.Your Bug Report should contain following information
Defect_ID – Unique identification number for the defect.
Defect Description – Detailed description of the defect including information about the module in which defect was found.
Version – Version of the application in which defect was found.
Steps – Detailed steps along with screenshots with which the developer can reproduce the defects.
Date Raised – Date when the defect is raised
Reference- where in you Provide reference to the documents like . requirements, design, architecture or may be even screenshots of the error to help understand the defect
Detected By – Name/ID of the tester who raised the defect
Status – Status of the defect , more on this later
Fixed by – Name/ID of the developer who fixed it
Date Closed – Date when the defect is closed
A sample bug report for your reference. This apart , your bug report will also include
Severity , which describes the impact of the defect on the application
Priority which is related to defect fixing urgency.
Severity & Priority could be High/Medium/Low based on the impact & urgency at which the defect should be fixed respectively
A defect could have a very low severity but a high priority
For example if there is an error in the text of the logo of flight reservation application , its severity is low since its can be fixed very easily and it does not affect any functionality of the system .But it needs to be fixed at high priority since you do not want to ship out your product with a incorrect logo
Likewise a defect could be high severity but low priority
Suppose there is a problem with Email functionality of Flight Reservation .This defect has high severity since it causes the application to crash but the functionality is scheduled to release in next cycle which makes it a low priority
