Bug bash, zbb and Software Quality

Bug bash Source and Significance

To do such an activity well, we must first understand the significance of the activity.

Bug bash(BugGeneral cleanup) originated from Microsoft, usually occurs at the end of each stage of project development (milestone called Microsoft), suchBetaBefore the version is released, specify a special time period (usually1-3Day), during this period, all the people involved in the project will focus on all aspects of the knowledge, use all the wisdom to search for the projectBug.

This is a very interesting activity, but it is not easy to organize it. There are generally the following key points:

(1) Although this is a test activity, participants are not limited to testers. Project managers, developers, and even senior management personnel should participate, just like the whole people. The purpose is to brainstorm;

(2Encourage departments and fields to search for each other, because new ideas and perspectives usually help to discover moreBug;

(3In order to mobilize enthusiasm and increase interest, you can introduce competition mechanisms as appropriate. For example, when the activity endsBugMost, most seriousBugIndividual, give material and spiritual rewards.

(4Can be divided into topics, such as security, user interface availability, internationalization and localization.

(5)As usual we'll have pizza and other fun food. Sometimes there's prizes for most bugs kept, most heinous bug, etc.

Zbb(Zero error rebound)--Software stability indicator

Why?Bug bashIn fact, it is closely related to another test method. Before that, let's talk about error convergence.

Error convergence

Error convergence refers to a turning point that the project team has made significant progress in reducing the number of active errors. At the turning point of error convergence, the speed of error resolution exceeds the speed of error discovery. Therefore, the actual number of active errors begins to decrease. The error convergence diagram is shown.

Even if the number of errors starts to decrease, the number of errors changes. Therefore, the error convergence generally only represents a trend, rather than a fixed time point. After the error converges, the number of errors continues to decrease until zero errors rebound.

Zero Error Rebound

Zero bug build: This version builds all knownBugAll solved.

Zero bug bounce: GenerallyZero bug buildAfter,BugThe number will rebound at an astonishing speed.Bounce. The system has to go through several timesBounce, Like Damping shock,BugThe number is fixed (or infinitely close) after several rounds)0. Ensure thatBugTo0To prevent pending issues.

Is60Personnel Team"ExpectationZbbChart". For each groupBugWhen the quantity is accumulated, It is the team'sBugTotal. The black line in the figure indicates the repairedBugTotal.

Zero Error ReboundIt means that at a certain point in the project, the development activities eventually catch up with the pace of testing and there are no active errors currently. After the zero-error rebound, the peak number of errors will be significantly reduced, and the number of errors will continue to decrease until the product is stable enough to build the first candidate release. A rebound in zero errors is a clear sign that the project team is gradually approaching a stable candidate release version.

Note that new errors will surely be discovered after this milestone is reached. However, it indicates that the project team was able to honestly report for the first time that no active error was found, although this is only for the current situation. In addition, it allows the project team to stay focused on this point.

In fact, it is throughBug bashTo achieveZbb.

This timeBug bashActivity Summary

This timeBug bashThe overall effect is not good, and the number of participants is small.BugNot manyBug bash. The reason is as follows:

1You do not really understand what we have discussed aboveBug bashThis is the primary reason for the low enthusiasm for product significance, rather than just taking it as a temporary activity. As a result, most of my colleagues did not make full efforts or even participate.Bug bashThe original intention of the activity;

2The activities organizer and department manager have different understandings about the activities. After the organizer released the test requirements, the department manager did not promptly emphasize the necessity and mandatory nature of the activities to the participants.Bug bashNo, it is unclear, and the organizer thinks that the department manager will have good cooperation and make these affairs arrangements in advance;

3Activities lack a good reward and competition mechanism, and cannot mobilize everyone's enthusiasm for participation. If there are some material or spiritual rewards and a competition mechanism is introduced, it can increase interest and motivate enthusiasm, truly engage in work and entertainment;

4The activity process lacks effective supervision and does not effectively supervise colleagues who have not participated in the activity;

5Low product stability, affecting testing efficiency

We hope we can make great improvements next time!