In the daily software testing work, after the tester finds the bug, the bug must be submitted next. Regarding how to submit a high-quality bug, it is a question worth thinking about, because it is related to whether the development can accept the bug, and it also determines whether the subsequent workflow can proceed smoothly.
The author specially summarized some small methods about submitting high-quality bugs, and shared them with you. The main points are as follows:
1. Ensure the validity of the bug
The submitted bug must be valid, so when we submit the bug, we need to determine the following points:
1. During the delivery process, testers need to classify and submit bugs according to the set modules;
2. The type of bug defaults to UI problem, function problem, crash problem, and it should not be confused when submitting a bug;
3. Whether the requirements are clear, whether the prerequisites are met, whether the input data is correct, whether the operation steps are clear, and whether the bug is unique;
4. Avoid submitting operational errors, repetitive, and known bugs.
Second, the bug title should be concise and clear
The bug title should explain the nature of the problem concisely, so that the developer can quickly understand the general content of the bug you mentioned. Need to specify which page to perform what operation and what phenomenon.
for example!
Correct example: After clicking save without filling in any content on my settings page, the client crashes.
Examples of errors:
1. Setting page save problem (too general);
2. The setting page crashes (the key steps leading to the phenomenon are missing);
3. The client crashes (there are only phenomena but unable to locate the problem location).
prompt:
1. The title break sentence symbol cannot exceed 1
2. The title cannot contain test process steps and module information.
Three, mark the test equipment
Submit bugs to indicate the device used for testing, device operating system version, test environment, network type, etc.
Four, indicate the prerequisites
Clearly point out the circumstances under which the submitted bug appeared. When the precondition of the bug is found to be empty, you need to fill in [None].
Correct example:
1. The WIFI network is normal
2. Account login is normal
Five, indicate the test steps
To describe how to reproduce the bug in a concise and clear step-by-step, the steps are ordered by number.
Write clearly the operation flow of each step according to the actual steps of your own operation, and which page or button you clicked last.
If a problem occurs in a specific situation, the following information should be clearly provided:
1. Accurately write the number of consecutive clicks, the duration of clicks and the duration of sliding up and down the screen;
2. Provide specific data for problems arising from specific data;
3. After accurately describing the path of the bug, describe the phenomenon.
Correct example:
1. Open the client and go to the home page -> click on the "My" page -> click on the user profile picture to enter the profile page;
2. On the profile page, click on the avatar and choose to take a photo -> click to save the avatar after taking the photo;
3. Return to the "My" page from the profile page to check if the profile picture is updated.
Examples of errors:
Menu bar in the upper left corner -> Login -> New user registration -> Enter mobile phone number -> Enter nickname -> Enter password -> Click "Get verification code".
Special reminder: Click in the test step to be connected with the [->] symbol
Six, attach screenshots and attachments
UI type: need to upload a screenshot of the bug, and add the corresponding red box mark;
Function type: the problem must upload the video file of the bug, the upload format is mainly MP4;
Crash type: You need to upload video and log, and the log must not exceed 10 minutes.
special reminder:
1. The naming of the attachment should correspond to the title;
2. Log capture cannot exceed 10 minutes;
3. The file name should not be too long.
The above are the things you need to pay attention to when submitting bugs. Of course, different companies and different projects may have slightly different standards, but they are basically applicable. Operating in accordance with these standards can basically ensure that you can submit high-quality bugs.
PS: Zhuoma Software Testing is a third-party software testing service organization that specializes in software testing [with CMA and CNAS dual qualifications]. It can provide various software testing services according to your needs and issue qualified and effective software testing reports. If you have test requirements, you can find Zhuoma Software for evaluation