Bug 5-bug report

Original article published on 12:04:11

In the previous four articles, we talked about Bug-related issues in general. We can only start to introduce more practical knowledge about bugs in this article. Starting from the bug report, the foreign name of the bug report seems to be better than the Chinese name-bug report.

 

In general, the bug report summarizes the bugs found.Defect managementWith the prevalence of tools, this type of report has gradually become meaningless, but I still want to start with this type of bug report-first, let's take a look at the components of a single bug. Let's look at a simple example of a bug:

 

Bug ID	Bug 783
Title	The "User Position" Field of the edit user information function is not saved.
Status	Active
Cause	New
Severity Level	2
Description	[Test Cases] Aaa_userprofile_0003 [Precondition] <Enter the Preset conditions here> [Descr resume ption] <Enter the detailed description here> [Expected] <Enter the expected result here> [Actual] <Enter the actual result here>

 

The above table is not an example of a complete bug, but it basically includes the basic elements of the bug. The following describes the basic elements:

 

1.Bug IDIt is a unique identifier of a bug, similar to a citizen ID card number. Each bug has only one unique ID number. For example, "bug 783" in the example"

2.Title Is a brief summary of the bug. For example, the "User Position" Field of the "edit user information" function is not saved.

3.StatusThe current status of a bug. For example, active means that a bug is active, that is, it has not been fixed by developers. The status of a bug is generally divided into three types: active, resolved, and closed, which correspond to the active State (which has not been solved by the developer ), resolved (the developer declares that it has been resolved but has not passed the RegressionTestVerified), closed (already repaired by developers and passed regression testing ). Changes to the three states of a bug will be discussed in subsequent articles.

4.Cause It refers to the reason for adjusting a bug to a certain state. For example, in the new example, the tester finds a new bug and changes the status to active. There may be multiple reasons for adjusting the bug status, even if the same status is different. This part of the discussion will also be discussed in subsequent articles.

5.AssignedIt refers to assigning a bug to the corresponding owner for handling. For example, Q Chen in an instance means that after the project personnel handle the bug, the bug is provided to Q Chen, the next handler. For specific candidates, different bug states have different requirements: The tester assigns the bugs found during testing to the developers of development-related modules or the developers of the development team responsible for Bug handling, the bugs handled by the development team are assigned to the testers who have detected the bugs.

6.PriorityCurrently in the test groupWorkThe severity level indicates that a bug is applied to an application orOperating SystemThe higher the severity of the bug, the higher the priority of the bug to be resolved. For example, instance 1 refers to a type of Bug with the highest priority (severity level). Such bugs need to be resolved as soon as possible. Priority of bugs will be discussed in subsequent chapters in this series.

7.DescriptionThis section is the most important part in bug submission and a detailed description of the bug information. For example, [test cases] aps_sheetjop_0003 ...... We can find that the "Description" is divided into several sub-modules to describe the bug information in detail and clearly, so that the bug-related personnel can handle the bug andOthersPersonnel are familiar with various information about each stage of a bug. In the next article, we will discuss in detail the content in the "Description.

 

The above is my opinion, if you have suggestions or exchange needs, please contact unique.wuchaodong@hotmail.com