Hard work beats talent when talent doesn’t work hard.
--Your friends at LectureNotes

Note for Software Testing - ST By VijayaKumar Thangavel

  • Software Testing - ST
  • Note
  • Computer Science Engineering
  • 1 Topics
  • 10 Offline Downloads
  • Uploaded 1 year ago
0 User(s)
Download PDFOrder Printed Copy

Share it with your friends

Leave your Comments

Text from page-1


Text from page-2

OVERVIEW What is defect?  Defect report  Origin of defects  Defect classes  Defect repository and test design  Defect examples  Developer/Tester support for developing a defect repository 

Text from page-3

WHAT IS A DEFECT?    A defect is an error or a bug, in the application which is created. A programmer while designing and building the software can make mistakes or error. These mistakes or errors mean that there are flaws in the software. These are called defects. When actual result deviates from the expected result while testing a software application or product then it results into a defect.  In different organizations it’s called differently like bug, issue, incidents or problem. When the result of the software application or product does not meet with the end user expectations or the software requirements then it results into a Bug or Defect. These defects or bugs occur because of an error in logic or in coding which results into the failure or unpredicted or unanticipated results.

Text from page-4

DEFECT REPORT ORBUG REPORT CONSISTS OF THE FOLLOWING INFORMATION:       Defect ID – Every bug or defect has it’s unique identification number Defect Description – This includes the abstract of the issue. Product Version – This includes the product version of the application in which the defect is found. Detail Steps – This includes the detailed steps of the issue with the screenshots attached so that developers can recreate it. Date Raised – This includes the Date when the bug is reported Reported By – This includes the details of the tester who reported the bug like Name and ID

Lecture Notes