What is the purpose of development and test engineers? The development is to realize the customer's needs, and the test engineer is to ensure the quality of the software. The two should be a win-win cooperation relationship, not a zero-sum game, not one trades off the other, or you win and I lose. Development and test engineers are actually very contradictory, the two are both antagonistic and unified.
There is no doubt that development and testing engineers should be opposed. If too much development interferes with the work of testing engineers, the work will not be carried out at all, the software quality will not be guaranteed, and the establishment of testing positions will be meaningless. There is no subordinate relationship between the two. Developers should not be afraid of bugs detected by testing. At the same time, testing should detect "more" bugs . This "more" is not more in quantity, but more in quality. The developed code has quality, what I want to say is that the quality of bugs is also a reflection of the testing level. The development cannot treat the test as the uncle, and the test engineer cannot put himself in the uncle's position.
The relationship between development and test engineers is also unified. I think that the responsibility of the test engineer or the sense of achievement of the test does not come from detecting bugs , but to help the development find and locate the problem. There is no primary or secondary relationship between the assistance here. The test engineer may not understand the code implementation where the bug occurs , and the developer may be too lazy to listen to the test engineer's opinion. At this time, it is not that the test engineer should work with the developer to find the problem of code implementation. , but to sort out the logic of the function together with the development, and the test engineer assists the development with testing experience and professional skills. The unified relationship between the two is reflected in the fact that this software is a common crystallization, not the result of the development party, but the purpose is to release the software faster and better.
I think in the computer major, the two directions of development and testing are similar to the science and liberal arts in high school. Most of them choose liberal arts when they are not good at math or grades in high school and think it is easy. Students who are a little "ambitious" in computer majors also choose to do development rather than testing. The label of testing is simple. Of course, this phenomenon and The analogy may not be accurate.
Test engineers should have a certain degree of professionalism when testing. The test should not be illogical and unplanned. This has a nice name - exploratory testing. for example:
Test: "There is a problem! Come and see so-and-so!"
Development: "How does it work?"
Test: "I just clicked and this appeared."
Developer: "Wait, I'll take a look at the background log, you can do it again."
Test: "Why can't it be reproduced? That's what I just ordered."
Development: "..."
This scenario is common, and it makes sense if the bug itself is an occasional bug . If you ask the test engineer how to operate, the test engineer will say, "I don't know, I forgot. But your problem is a bug ." It takes a lot of development time to troubleshoot this problem, isn't it? Not letting you test is a test that allows you to have routines and ideas. This is a test engineer's own literacy problem.
The same is true for developers. Self-testing is a good habit. Aside from the ability to develop code, this is the most basic quality for developers. for example:
The developer's heart: "Finally finished this function, it's unexpected, anyway, there is a test, let them test it, and then fix the problem."
Most of the bugs are because the development itself has not done a good job of self-testing. Unit tests are not available in every project and every module in every company. Even many developers with several years of work experience do not know how to write unit tests. Think that your job is to write code, and the work of checking whether the function is complete and whether there are bugs should be handed over to the test.
Whether developing or testing, it's just a job, work hard but don't have personal feelings. If you feel hatred, please be clear about public and private, and stick to the villain in your heart; if you have indescribable feelings, please keep a low profile. After all, IT work is already very hard, and you can no longer abuse dogs.