Test floret &; Grass: Why?

Programmer Xiaoshu: I just don't want to change. Why?

Kao Xiaohua: Why don't you change it? If you say no, you won't change. Xxxxx, two people together. .....

Grass inspection: if you don't change it, you won't change it. Then I'll turn it off. .....

Obviously, the practices of small trees, small flowers and grass above are all wrong, so what are the more reasonable solutions?

First, find out why the bug is unchanged:

1, the development can't be copied locally, and I feel that the bug is gone.

Solution: Help develop and reproduce bugs. If there is no problem with local development, but there is a problem with the test environment, pull the development over and compare the differences, so that the development can be reproduced as much as possible. At the same time, reflect on whether your bug submission is correct and the steps are clear. If not, modify the bug content in time.

2. The 2.bug needs to be operated in multiple steps, which is complicated, and the developer thinks it is unnecessary to modify it.

Solution:

A, personal charm (don't underestimate this, it is still very important to have a good relationship with development)

B, from the user's point of view, analyze what will happen if the user encounters this problem after going online, and try to convince the developer.

C, find product confirmation, explain the details of the problem, the possible consequences, the product will make the final decision or convince the development together with the product.

3. It's almost online. The bug was found too late and hasn't been fixed.

Solution: First of all, it depends on the priority of this bug. If it really affects the user's use and experience, it must be solved before going online. One is to delay online time, and the other is to work overtime to solve bugs. If not, the final decision is still given to the product and judged by the product.

4. It involves the modification of the framework, and the modification cost is too high. This version will not be changed for the time being.

Solution: Find other technology giants in the company, see if there are really no other alternatives, list the possible risks of the products, and then decide.

5. I can't solve the problem of third-party plug-ins.

Solution: Find the corresponding colleagues, contact the staff of the third-party plug-in, and try to push the third party to fix this problem as much as possible.

In short, different treatments should be made according to different situations. You can't just close the bug by one sentence of development, and you can't be obsessed with development because of an irrelevant problem, which will affect the testing progress of the whole project.

Two other humble opinions:

What should I do if I encounter a Bug where the product does not change?

What should I do if I encounter a Bug that cannot be reproduced?