Foreword
In a speech on the Quality Week, Microsoft's test manager, Roger Sherman pointed out the main cause of BUG shutdown due to "irrecentre". This is a very unfortunate situation, because such bug report isted to waste the valuable time in the intense development plan, increasing the quality of the product is completely irrelevant, and also leads to the sense of frustration between developers and testing and Poor feel. Sometimes Bug Report is a tool and configuration due to inconsistency between short or random events, testing and development, or a fuzzy definition of the correct behavior in the test environment, but many of them are not reproduced. The closed test report is because the description is not clear, misunderstood, or just a text error.
?
Fortunately, I have learned some of the best Bug Report that can cause management to pay attention, clearer and developers and get repaired. These techniques not only provide a reliable return on the proportion of the problem that is repaired, but also rewards in the adoption of developers and management. Using this method in the project I managed to write bug Report, only one of Bug Report is not fixed.
?
The idea of this article is only when your report is a professional quality work. Smart execution of a complete test package is one of the factors that produce reliable test status information. A variety of methods for how to construct such a test package are widely introduced in many test literature. Choose techniques that are consistent with your quality risk management and make it adapt to your specific situation, and agilely supervise the implementation process of the planned test so you can have a reliable test implementation process.
?
Another key factor-Bug Report, but not much attention. This is very regrettable, because excellent bug reports are very important as testing themselves with the true and understandable work of the test team. Imagine: If you can't use the term to be able to understand the developer and explain a mistake to the developer in the method that can be used for debugging, how can he fix the problem? If you are not able to raise an error summary like "Bumper Sticker" in bug Report, how do you let them care about the questions you discovered?
?
The core of bug Report is a description of the error. Table 1 is an example of a good and poor error description. Writing Bug Report is a good art form. The following 10 techniques can help your team improve the quality of the bug Report:
Organize Structure: Test staff should perform tests well-thoughtable, be careful, and do a detailed record. This can prompt them to have a good understanding of the system under test. When the error occurs, an organized testers can know the earliest question: Reproduce: Test staff must reproduce the problem before writing bug report. If the error is no longer reproduced, it should still be written, but the occasion of the problem must be explained. A good processing principle is to try 3 times before writing bug Report. Isolation isolate: You must try an isolation error before trying to write bug Report. It can be used to change some variables, such as the system configuration, which may change the symptoms of the error. This information can provide ideas for developers. Summary Generalize: After the tester discovered an isolated and reproducible problem, the problem should be summarized. Does the same issue appear in other modules or other places? Is there a more serious problem with the same fault? Contrast Compare: If the tester has previously verified the current error test case, then he should check the previous test results to check if the same condition passes through the previous test. If so, then this problem is like a return of an error. Note Because the same test conditions may appear in multiple test cases, this step is not only to check a test case in the previous result. Summarize Summarize: The summary of the error in the first line of Bug Report is critical. Test staff will spend some time to think about what is discovered. This not only requires reports prepared by testers to attract readers, making the communication with management, and help set the priority of the error repair. Streamline Condense: After completing the first draft of Bug Report, the tester should read it repeatedly and concentrate on the steps or words that do not have the relationship. Including or blurred instructions and those who have the end of the Bug Report due to the details of those who do not have any relationships or those who do not need to reproduce the error. Eliminate ambiguity Disambiguate: Test staff should be carefully checked if the report will have misunderstandings while streamlined. Test staff should try to avoid blurring, generating ambiguity and subjective words. The goal is to use the fact that the facts can be expressed, clear, and does not produce the words of the dispute. Neutral Neutralize: As described in the article, as a bad news transmitter, and the good submission message is a challenge. As with all incorrect summary, independent bug report should be fair in terms of wording. Attacking developers, accusing potential errors, attempting or useing medication will cause the developer's disgust, and make attention from "improve product quality". This big goal is transferred. Careful testers use only bug report to describe the facts. Check if the tester feels bug report is the best version he can write, he should check the report again to check one or more peers. His colleagues should also give some suggestions, in order to clarify the problem, if appropriate, even challenge the conclusions of "errors". In the allowable time, the test team should submit the best bug report as much as possible. ?
The above 10 techniques can help you and your team submit accurate, completely researched, careful ideas, high quality technical documents. The test team should focus on the task of bug Report, the test team leader and manager should make the test group members clearly recognize that the writing of excellent bug report is a primary task. Measuring excellent Bug Report should include the following:
o ??????? For management, it is clear, especially in summary this level;
o ??????? It is useful for the development department, mainly to give relevant information about the development of the developer's efficient debugging problem O ??????? can quickly change bug from "OPENED" status As a "closed" state, it is reduced to get more information from the Different Bug Report returned from the developer and leads to the time of the test personnel.
?
The process of improving the BUG report is to take some time, but it also gives a significant return. First, a simple process improves the communication between the test team and the high-level, parallel management, enhances the trust, prestige, and encourage management to invest more resources to test investment. Second, a smooth submission of reports to developers have promoted positive relationships between testing and developers. Third, a shorter bug life cycle is more effective, spending the time to prepare excellent bug report on the time of the time before time and the time of the bug Report spended by the rework These rewards help the development process achieve better product quality through efficient communication and high efficiency processes.
?
Good bad
Summary
Arial, Wingdings and Symbol fonts destroy new files.
Steps to reproduce the problem (Steps to reproduce):
1. Start the SpeedyWriter Editor and then create a file.
2. Enter 4 lines of text, repeat the "The Quick Fox Jumps Over The Lazy Brown Dog",
3. Select 4 lines of text, click the drop-down menu of the font, select Arial.
4. All words are converted to control characters, numbers, and other binary data.
5. Try 3 times, you can reproduce this problem each time.
ISOLATION
This problem is new in Build 1.1.018; the same test case is tested in Builds 1.1.007 (System Test Entry) and 1.1.017.
This issue can also be reproduced using Wingdings and Symbol fonts, but Times-Roman, Courier New and WebDings are not available.
Based on blurred guess, this may be just a problem about formatting. Save this file and turn it off again, then open the file, this error still exists.
Save the file before converting the font will not generate this error.
In the already existing file, this error will not be generated.
This error only appears under the Windows98 platform, this problem does not appear under the Solaris, Mac or other Windows platform.
?
When some text is a Arial font, all the content I created is destroyed.
?
