Mr. Wang is a new member of a test team. What should he do in this situation?

Mr. Wang is a new member of a test team. This is the first time he participated in the R & D process. he is conscientious and responsible. He can always find bugs in products accurately and quickly, and help the development team find root cause.

However, as the project goes on, more and more bugs are accumulated. as the progress lags behind, everyone is under great pressure. slowly, Mr. Wang discovered some subtle changes in the situation around him. for example, he used to find a bug and everyone would encourage him. Now he finds some less serious bugs, as if some team members were not so nice-looking. in addition, He vaguely heard that the test Manager seems to be in conflict with the Development Manager. the main reason is that the progress cannot be kept up. The developer wants to push some bugs that have been decided to be fixed later, that is, he hopes to wait until the next version is repaired.

At the same time, Xiao Wang's good friend, xiaoma, developed for several years and quietly told Xiao Wang. the progress is lagging behind, and there are too many bugs. The big boss mentioned above cannot read the reports. If it is difficult, everyone will not be able to eat well in the end. now, even if the number of bugs can be found, it is too late to repair them. In addition to making the reports more ugly, it is not good for the end customers. It is a thankless thing...

Mr. Wang has a half-year interview with the Test director. in response to this situation, Mr. Wang also summarized the following issues. if you are the Test director, how do you suggest Mr. Wang handle the current situation?
(I will announce the answers from the Test director and my own opinions tomorrow)

 

 

1. generally, in the project preparation stage, a defect level (bug bar) is set up to define the severity of the defect. as the project progresses, should the defect level change, or should it remain unchanged?

2. when a bug is found, the severity of the bug is defined based on the defect level, such as Level 1, level 2, or level 3. after a bug is detected and assigned a corresponding severity level, is there any other cause that the current severity of the bug changes? For example, after research, it may take a lot of time to fix a bug. Does this change the severity of the bug?

3. What are the factors for fixing or not repairing bugs found? In addition to the severity of bugs and the impact on users, does the current team's progress and resources affect decision making? For example, if some bugs have been prepared for fixing and the development progress has been delayed, will the system decide not to fix these bugs?