Day 2.3 : What is Bug?

What is Bug?

A bug is the consequence/outcome of a coding fault.

Defect in Software Testing

Defect in Software Testing is a variation or deviation of the software application from end user’s requirements or original business requirements. A software defect is an error in coding which causes incorrect or unexpected results from a software program which does not meet actual requirements. Testers might come across such defects while executing the test cases.

These two terms have very thin line of difference, In the Industry both are faults that need to be fixed and so interchangeably used by some of the Testing teams.

When testers execute the test cases, they might come across such test results which are contradictory to expected results. This variation in test results is referred to as a Software Defect. These defects or variations are referred by different names in different organizations like issues, problems, bugs or incidents.


Bug Report in Software Testing

Bug Report in Software Testing is a detailed document about bugs found in the software application. Bug report contains each detail about bugs like description, date when bug was found, name of tester who found it, name of developer who fixed it, etc. Bug report helps to identify similar bugs in future so it can be avoided.

While reporting the bug to developer, your Bug Report should contain the 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 maybe 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
  • 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



Comments

Popular posts from this blog

Day 2.2 : What is STLC

Day 1

Day 2.1 : What is SDLC?