Shulou(Shulou.com)06/03 Report--

directory

I. Precautions for Reporting Defects

II. How to prepare defect reports

On some projects, defect reports are the primary work output of test engineers. A good defect report can help developers quickly locate problems, help product managers understand the severity of defects and user quality information, and quickly determine repair priorities; in regular meetings of the project cycle, it can effectively improve meeting efficiency; if the test is provided as a third-party company, the project team will evaluate the tester's work ability and professionalism based on the quality of the defect report. Therefore, writing a high-quality defect report is one of the important basic skills of testers.

First of all, the purpose of defect reporting is to solve defects, but because each role in the project team has different responsibilities and different positions towards defect stations, it is very important to make convincing and complete defect reports.

When submitting defects, describe clearly the steps and severity of the problem.

A common problem encountered by testers during testing is that submitted defects are developed to be irreproducible, or submitted user suggestions are marked as not fixable by requirements. If the tester cannot clearly describe the problem steps or does not mark the specific environment or tools, the development is likely to fail according to its own environment, and if the user suggestions are not explained to the user, they will not be repaired by the product due to the time limit.

Each company has different reviewers for defect reports, which requires testers to pass correct and effective information to reviewers from multiple angles. When using Bug management tools, pay special attention to choosing a good priority. If it is submitted locally, it is also necessary to indicate the priority. When testing, we should always think from the user's point of view, rather than whether it is important for developers to define bugs themselves. Second, testers need to pay attention to whether the network service under test outputs enough logs. In the long run, more logs will help the test find errors and locate problems faster. Instead of keeping yourself in a black box. In addition, if compatibility problems are found, such as page exceptions in weak network conditions when performing specific operations, similar problems need to be evaluated by testers themselves, read requirements specifications, ask relevant requirements personnel, the frequency of possible occurrence of specific operations, and specific user usage habits.

2. Early submission of defect reports

Near the end of the project cycle, if there are new Bug submissions, the development will evaluate the possibility of introducing new defects, and the repair will need to return to the entire Module to complete the test, or the higher-risk defects will not be fixed temporarily. Therefore, what testers need to do is to formulate a good test strategy when making a test plan, try to find serious bugs in the early stage of the project, and submit the defect report as soon as possible.

3. Submit all bugs that are difficult to reproduce

Avoid submitting duplicate bugs if you have multiple tests on a project;

After passing a round of tests, you can search the Bug distribution in the Bug management system. For example, if you see which part of the problem is relatively distributed by module, function or type, it is likely that more bugs will be hidden there.

When the tester cannot judge whether it is a Bug, he can record it first. If it involves core functions, he can ask the requirements personnel in time. But it can't be left out.

For bugs that are difficult to reproduce, testers need to write down all relevant information as early as possible and mark the frequency of recurrence. Try as many times as possible and what special factors trigger it.

For bugs that are difficult to reproduce, one can use the server log to query the error content, and the other can deploy the corresponding screen recording tool to solve them before testing.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.