Specification for reporting software test errors

The purpose of reporting software test errors is to ensure that the person who fixes the error can repeat the reported error, thus facilitating the analysis of the cause of the error, locating the error, and then correcting it. Therefore, the basic requirements for reporting software testing errors are accurate, concise, complete and normative. The reporting techniques to be mastered are summarized as follows.

1. Description (Description), concise, accurate, complete, revealing the nature of the error, recording the location of defects or errors

Description to accurately reflect the essential content of the error, short and clear. It is a good practice to include the user interface (UI) when errors occur in order to make it easier to find a test error in the software error management database. For example, a record dialog box title, menu, button, and other control names.

2. Specify the type of error: layout, translation, functionality, Double-byte

According to the wrong phenomenon, sum up the type of judgment error. For example, layout errors, translation errors, functional errors, and double-byte errors are the most common types of defects or errors, and other forms of defects or errors fall into one of these forms.

3. Use the automatic numeric serial number between short lines, using the same font, font size, line spacing

The use of automatic numeric serial number between short lines, using the same font, size, line spacing, you can ensure that the record format consistent, to standardize the professional.

4.UI to enclose quotes, single quotes, double quotes are recommended

UI with quotes, which makes it easy to distinguish between UI and plain text for easy resolution, locating defects, or errors.

5. Try to record only one operation per step

Ensure concise, orderly orderly, easy to repeat the operation steps.

6. Confirm the procedure complete, accurate, short

To ensure rapid and accurate repetition of errors, "integrity" is no omission, "accurate" that is the correct step, "short" that there is no unnecessary steps.

7. Choose how to capture the image according to the defect or error type

In order to visually observe defects or errors, an additional defect or error interface is usually required, attached as a bitmap as an attachment in the "Attachment" section of the record. In order to save space, but also to reflect the true nature of defects or errors, you can catch defects or errors produced by the full screen, active window and local area. In order to quickly locate, correct defects or error locations, it is often necessary to attach a Chinese-English control chart.

8. Attach the necessary special documents and personal suggestions and annotations

If you open a particular document with a defect or error, you must attach the document so that you can quickly reproduce the defect or error. Sometimes, in order to make a defect or bug modifier more explicit about a defect or error, you can attach a personal modification proposal or annotation.

9. Check spelling and grammatical errors

Check spelling and grammar before submitting each defect or error to ensure that the content is correct and the correct description of the error.

10. Use industry-idiomatic expressions and expressions as much as possible

Use the industry's idiomatic expressions and expressions to ensure that the expression is accurate and embodies specialization.

11. Common UI to be unified and accurate

The UI of the error report is consistent with the software UI of the test, making it easy to find positioning.

12. Use phrases and sentences as much as possible to avoid complex sentence patterns

The purpose of the software error management database is to facilitate locating errors, therefore, it requires objective description of the operation steps, no cosmetic words and complex sentence patterns, enhance readability.

13. Each error report includes only one error

Each error report includes only one error, which allows the bug fix to quickly locate an error and focus on correcting only one error at a time. The verifier verifies that only one error has been corrected at a time.

The above summary of the report test error specification requirements, with the software testing requirements are different, testers after long-term testing, accumulated a corresponding test experience, will gradually develop good professional habits, and constantly add new specifications to write requirements. In addition, regular reading, learning Advanced Test Engineer's Test error report, combined with their own previous Test error reporting to compare and think, you can continue to improve skills.