Logging Bug/Defect

How do you log bugs?


In software testing, the bug report is a detailed document detailing the flaws discovered in the software application. The bug report comprises every detail regarding a bug, such as the description, the date the bug was discovered, the identity of the tester who discovered it, the name of the developer who corrected it, and so on. The bug report aids in the detection of similar bugs in the future, allowing them to be avoided.

My Bug Report should include the following details when reporting the bug to the developer.

  • Defect ID — The defect’s unique identifying number.
  • Defect Description — Detailed explanation of the Defect, including information about the module where the Defect was discovered.
  • Version — The application version in which the flaw was discovered.
  • Steps — A detailed set of steps with screenshots that the developer can use to reproduce the issues.
  • Date Raised — Date when a Defect Is highlighted
  • Reference — To help explain the fault, include references to papers such as specifications, design, architecture, or even screenshots of the error.
  • Detected By — Name/ID of the tester who reported the issue
    Status — The defect’s current state; more on this later.
  • Status — The defect’s current state; more on this later.
  • Fixed by — Name/ID of the developer who made the fix
  • Date Closed — The date on which the defect was resolved.
  • Severity — the fault defines its influence on the application.
  • Priority — that is related to the urgency of defect correction. Severity According to the impact urgency with which the issue should be corrected, the priority could be set to High, Medium, or Low.

Comments

Post a Comment

Popular posts from this blog

Design Phase (SDLC)

  What would you do during the design phase in SDLC? The Design Phase is an crucial phase of the  Software Development  Life Cycle. The list of requirements that you develop in the definition phase is used to make design choices. In the design phase, one or more designs are created to achieve the project result. Depending on the project subject, the design phase products includes flow-charts, sketches, site trees, HTML screen designs, photo impressions, prototypes, and UML schemas. The project supervisors use these designs to choose the definitive design that you can produce in the project. The development phase follows it. Once you have selected the design in the definition phase, you cannot make changes in the project’s later stage. The objectives of the SDLC Design Phase are as follows: Objectives Successful completion of the SDLC Design Phase comprises: Transformation of all the requirements into detailed specifications covering all the aspects of the system. Planning...
Read more

UseCase Vs TestCase

What is the difference between use case and test case? Use Cases  and  Test Cases  are two important terms in context of Software Testing. A use case tells how a System will behave or perform a certain task provided the given conditions and a test case contains the actual test data, set of instructions to system and expected result of the interaction with system. Following are the important difference between Use Case and Test Case. Sr. No. Key Use Case Test Case 1 Objective The objective of Use case is to ascertain a certain output after the set of operations. The objective of test case is to ensure that system is working fine for each given instruction and yields the required result. 2 Definition Use case is a representation of actions which describes the behaviour of system to do a particular task. Test case contains the test data, set of instructions to follow and a result(s) of following the instructions. 3 Source Use cases are prepared on requirements. Test cases ar...
Read more

TestCase Vs TestScenario

What is the difference between test case and test scenario? A test case is a set of criteria that a tester uses to verify whether or not a software application is meeting the customer's requirements. Preconditions, case name, input conditions, and intended outcome are all included in the test case design. A test case is a basic activity that is derived from test scenarios. It is a comprehensive document that comprises all potential inputs (both positive and negative) as well as navigation instructions for the test execution process. Writing test cases is a one-time effort that may be reused for regression testing in the future. The test case contains thorough information about the testing approach, procedure, preconditions, and expected results. These are used during the testing phase to see if the software program is capable of executing the purpose for which it was created. By associating a defect with a test case ID, test cases assist testers in defect reporting. The testing tea...
Read more