Usually accumulated, there is from the forum, there is from the book, and there is also his own Hu Yu :)
1. 2004-2-20 BUG definition BUG is more than just a code level error, but it can be a defect found in the design and test phase. Whenever, any proposal that helps improve product quality, any need to pay attention to problems worth tracking, any potential errors, can and should be used as a bug. Therefore, in the software development process, the management of BUG is critical. Scientific practice is to record, track, manage BUG subsequent changes and processing schemes by tools.
1) Timely dispatch and repair BUG is not enough, PM or DEV LEAD should * timely * Dispatch BUG to Corresponding Developer to FIX according to bug Description and Stack TRACE, and specify a FIX by when . 2) Detailed bug description at this point, also puts a certain requirement for Tester. During the test, the problem of the light discovery software itself is not enough, when an error (sometimes Memory Crash, A / V, Assert, etc.) should also record the Call Stack and write "BUG Tracking System". Some bugs are difficult to repro, but a detailed bug description can help the BUG's FIX.
2. 2004-2-20 BUG's handling from management this level, once the BUG is discovered, the most difficult does not to record, assign people to solve, and track. The most difficult is to decide to delay some bugs, and even don't even resolve. Such bugs are often discovered in product development, and is due to the defects of the original architecture design, solving such bugs requires a lot of human and time, the influence surface, may introduce new bugs. For such bugs, PM should contact clients, such as market sectors, technical support sectors, and even earlier intervention. If you have no influence from their feedback, it is decided to delay, or not resolved, if you have no influence of this BUG migrate.
There are still some follow-up work for these decisions, or BUGs that are not resolved. First of all, you will be resolved in the next release; secondly to let the relevant technical support staff are deeply understood, ready to be planned.
3. 2004-2-20 Microsoft's experience in Microsoft, when the coder is difficult to achieve a function, it is generally experienced the following procedures: (1) The coder will find the law to solve, including colleagues advisory. (2) The coding personnel take the lead in the technology of the department. (3) The coding personnel discussed discussions at the project's regular basis. (4) For the project manager organization and related other department staff. (5) Opinion by the project manager to listen to the market departments and customers.
Generally, after (4) and (5), the problem is more complicated, not simple measures can be solved. There are two possibilities at this time, one is that the function to achieve is not much affected by the customer. In this case, it will cancel this function (it should be said to the next version). The purpose of this is to make the project according to the plan, let the products put on the market as soon as possible. The market is like the battlefield, and the occupation as soon as possible is more important than the intimate profit. Another function that may be implemented is very affected by customers, and there is no such function product will lose a lot of markets. In this case, many will adjust the project plan, and the human material will overcome this difficult relationship, and other parts of the project may be suspended in the case where the problem is not resolved. The purpose of this is to ensure that there is no product without market competitiveness. The accuracy of these two decisions is based on the full grasp of the market and the full understanding of customers. This is another weak point of China's software companies. How many software companies in China attach importance to market and sales like the development of project development, attach importance to customers, after-sales service and technical support like attention?
4. 2004-2-20 BUG-related minimally invasive BMS system defines the association between bugs, 5 types: dependencies, repetition, related associations, file associations, accessories
Dependency: a bug solution relies on other bugs, for example, programmers B BUG is only able to solve after the programmer A's bug is resolved, a version of a bug in the previous version, or even a product BUG relies on the bug of other products. Relying on the relationship is indeed complicated, but the proportion of general use is relatively small as much as personal experience. If there is dependencies between bugs, the bugs that are dependent (or parent dependence) should be resolved as soon as possible.
Reconciliation: If one of the defects is actually another defect defect, it is necessary to establish a repetition association between the two defects. We asked the tester to try not to repeat the bug as much as possible. They have been resolved.
Related Relations: The concept of related associations is simple relative to dependence associations and duplicate associations. In the same database, there is a certain relationship between a defect and other defects, but it is not dependent on the relationship or repetition, it can establish associations for them. There is no dependency between various defects associated with associated associations, which means that various defects can be handled independently.
Repeat associations and attachments: The former is because each Test is likely to register repetitive bugs, because the latter is not clear, directly uploading a picture effect is much better. Of course, the link to a file is also good.
Some functions are more powerful BUG management tools to associate BUG and the corresponding Test Case to associate BUG with the Change Number (or file number) in the source code management. Of course, a BUG management tool is the most basic operation is New, Resolve, Close, Assign, and Query queries. It will have great improvements in the quality of these most basic operations.
5. 2004-2-20 BUG Management Tool Rational ClearQuest Nice, process, operation, bug information, etc. can be customized, different queries, charts, etc., and can automatically issue E- according to pre-defined E-mail rules. Mail. The best is that she has a tutorial (English version, but it is very easy to understand)
