Bug 3-"Custom" bug

Originally published on 13:34:58

The so-called "Custom" refers to the fact that many software projects do not have "product manuals" or are not qualified "product manuals.

 

In the previous article, I introduced the bug's "official" definition and personal opinions, which involved the "product manual" which is still the product of idealism for some current software projects, in this article, I will share with you a similar project experience that I have experienced before. Of course, I will also give you some "remedies ".

 

Different people may have different opinions on the same issue. That is to say, "One thousand hamwright in the eyes of one thousand viewers. This sentence is used to describe developers andTestThe attitude of the personnel to the bug is more appropriate. Many times, when a tester finds and submits a bug, the developer's response is "This is not a bug" (this is not a bug) or "this is not a serious bug ."MoodIs quite frustrated, and then turned into anger.

 

There is no "product manual". Why is this a bug? This is indeed a problem. The problem is solved by nature, so we must have managed it. The most direct and naive idea may be to establish a sound mechanism. Will the Product Specification be completed soon after. It's really a good solution, but it's too idealistic. It's just like the group of mice in the story of the mouse bell. The solution is good, but it's not feasible or difficult to implement. A reasonable set of software processes is not a matter of time. Moreover, a sound mechanism cannot completely eliminate undefined bugs. What should we do? Another way is to discuss it.

 

Prior to the discussion, the tester made some preparations.WorkWhat to do. We should list the sins of "Bug. In this case 《Software TestingThe above things seem to be pale and powerless. After all, this is the tester's "Bible" but not the developer's. The exaggeration is like two people who believe in different religions. It can be said that a person who believes in God, a person who believes in Allah, and you ask the people to follow the Americans to believe in Christianity, it seems a little too much. What's more, the things mentioned in the Bible are also extensive, and they do not strictly point out what the bug looks like. At this time, a more reasonable way is to list your own considerations, and also have more convincing practices-find the same or similar functional points in well-known software products that can prove your opinion, in this regard,Microsoft"Can help a lot ".

 

The two sides began to discuss whether this was a bug based on a realistic attitude, just like a court debate. The tester acts as the plaintiff's attorney, the developer acts as the defendant's attorney, and the Project Manager acts as the judge. Remember, we only come from lawyers, so the verdict will not directly affect us. Therefore, testers should never treat themselves as plaintiffs, developers should not regard themselves as the defendant and his father (but often in this case, testers regard bugs as their trophy, but the software that developers have worked hard to create ), we should look at this "bug" with a rational attitude ". After the session, the plaintiff's attorney presented his views, followed by the defendant's attorney's statement, then both parties held a brief peaceful and friendly debate, and then pronounced the verdict that no appeal was allowed.

 

Of course, it should be noted that this meeting should not take up too much time, and there is no need to officially invite a large group of people to the Meeting, but after the meeting is complete, both Parties shall accept the discussion results unconditionally and handle them in a timely manner.

 

Many of the projects I 've experienced have been the final victory of testers, not because I am strong or aggressive, more often, after I come up with examples of the famous software and explain why it should be done, the developers will accept this explanation. Of course, sometimes testers do not understand the knowledge of software products and lead to false positives and bugs. At this time, testers should accept "This is not a bug" with good faith ", at this time, any redundant actions or words are invalid. They will not only bring you any benefits, but also bring an inharmonious factor to the project team. In the age of building a socialist harmonious society for all, everyone must be harmonious ~

 

The above for personal opinions, if you have suggestions or exchange needs, please contact unique.wuchaodong@hotmail.com