Test Development Engineer Growth Diary 007 - Bug Priority Definition and Filling Specifications

First, bug priority definition

Goal:

Standard test the level accuracy of submitted bugs, and can internally agree on bug levels and repair time specifications.

Instructions:

1, Emergency/Fatal:

● Affects core main functions; such as form data cannot be submitted, forms cannot be created, processes cannot be triggered, reports cannot be previewed, etc.;
● Affect the normal use of the project and the progress of construction, according to the requirements of project feedback, such as customer demonstrationsWait for the issue that needs to be fixed on the same day;

2, high/critical

● Problems affecting the execution of test cases of the test function;
● Problems affecting high-frequency/common functions, such as the search failure of the form management page;
● Bugs affecting the normal use of the project, do not affectIn the follow-up construction, the project feedback the problem that the repair time is not the same day;
● The problem that the internal and external services/modules that depend on cannot be used normally;
● The performance problem, the project clearly requires that the front-end and back-end processing be arranged as soon as possible;

3, Medium/Fair

● General functional issues, which can be dealt with iteratively in the current month;
● Issues with obvious typos;
● Performance issues, special issues that can be dealt with according to the normal R&D schedule;

4, low/hint

● Problems that do not affect functions, such as prompt copy, page UI, page copy optimization

5, irrelevant/recommended

● Content that belongs to the perfect system/user experience/suggestion type
● It can be submitted to the legacy pool/demand pool without being processed with the current iteration, and the corresponding R&D/products will be processed by human beings

Second, bug form filling specification

Goal:

Clarify the content specification of the bug sheet submitted by the test, and avoid the situation of secondary communication and confirmation of the bug sheet confirmed by R&D and testing.

Instructions for filling out:

Title:

● Required
● "Specific object + brief description of the problem" is recommended

Environmental Information:

● Required
● Include the environment address, application name, and page name, so that the front and back ends can be reproduced and viewed;
● If there is a problem with the project version, the current corresponding service version information needs to be supplemented;

Steps:

● Required
● If there is a screen recording/screenshot, you can briefly describe the steps. If there is no screen recording, detailed and clear steps are required;2 and 3 identify the sequence of steps

Expected result:

● Required
● You need to fill in the correct return result/display content or paste the correct renderings, and frame the key content
● If it is a project, you need to fill in the information that you want to fix in the corresponding version;

Actual Results

● Required
● Accurately describe the results and the corresponding screenshots of the problems. If necessary, you can select the key content in the screenshots or the interface return information such as comparison

Preliminary Analysis

● Not required; if it's just copywriting, UI display problems, you can leave it blank; other errors are suggested to fill in
● Front-end problems: the console saves information; the error content of the front-end console;
● Back-end problems:Interface information, in the packet capture page, right-click copy_cURL(bash) on the corresponding interface, and paste it into the bug list;
● Backend problem: log information, corresponding log error content, screenshot or copy content;

Additional information

● Iteration: Select the corresponding time to schedule the repair release iteration; if there is no corresponding option, you can create an iteration first;
● Module: select the corresponding module;
● Processor: select the corresponding front-end/back-endYou can choose more than one;
● Priority: select according to the priority definition;
● Defect type: select the corresponding one according to the actual situation: front-end problem, back-end problem, front-end problem, optimization suggestion,Other (when not the first four items)