How do testers handle the relationship with developers?

The test is independent. Ensure that the definition of software functions is meaningful. If you feel so strongly, learn to say "no" The specifications defined by the project manager can also be changed (so can the specifications of PM). Insist on what is right (feedback PM/DEV to the project manager and developers). Be patient and generous (team building). "Communication" is a very popular word, not just testing. Now every industry is talking about communication, and there are special courses, which always makes me feel. It seems that the testing industry is not immune. For example, almost 65,438+0,000% of all the introductions you can find about the basic literacy of test engineers say that excellent software test engineers need good communication skills and a sense of humor. When I was young, I always felt that the testing industry must have the eloquence of Degang Guo or Wu Zongxian, or be suitable for people who are as amused as Mr. Bean. However, during my working years, some test engineers I have come into contact with are taciturn and rigorous, some like to laugh and tell jokes, some are impatient, and some seem to be in no hurry to get angry. I realized that communication is really not that bad, as long as I speak fluently, have no serious stuttering, are not too withdrawn or have serious mental illness, as long as I am an ordinary normal person. After all, when dealing with a development or project manager, the most important thing is the quality of what you measure. Of course, a foreign language can be regarded as a kind of communication ability now, but it depends on the specific environment. If you want to speak a foreign language when you are in contact with all compatriots in the motherland, there is nothing you can do. Talked for a long time, as if communication was completely unimportant. In fact, there are still some principles or skills to pay attention to in practice. If you pay more attention to daily details, you may become a tester popular with the broad masses of the people. In fact, testers have to deal with many people every day, including project managers, customers, developers and so on. But the people who interact most may be developers, the so-called "small partners", so let me briefly talk about the principles that testers need to communicate with developers in their work. This kind of thing is a matter of opinion anyway. If you make a mistake or feel that what the villain said is not deep enough, just smile and feel happy. The first point: the goal is the same. Although the nature of our testing and development work is opposite to some extent, the ultimate goal is actually exactly the same. At a higher level, all this is for the company to produce a good product or make a successful project. Further down, we all come out to work, and we have no grudges with past developers. In any case, we must be worthy of the boss and do a good job for it. When we understand and master the principle of consistent goals, it will be much easier to communicate with developers. Of course, it is not enough to stay in our own minds very clearly. It's just that the Long March took the first step, and now everything needs to rely on hype. When communicating with developers, you should let them recognize it through various methods or channels. At the very least, let developers feel that they are in the same boat as testers, and everything is as good as brothers. Of course, this is easy to say and needs flexible application and use. It is absolutely impossible to secretly and viciously report on developers, otherwise it will be empty talk. Sometimes if something really goes wrong, don't blame the developer. Sometimes it is necessary to take a bullet for them if it is not too serious. In short, testing and development are the closest comrades! Chairman Mao said: "We are all from all corners of the country and come together for a common revolutionary goal!" ! "The second point: professional self-confidence, the principle value of insisting on inspection lies in our profession. In every professional output document, every professional discourse or suggestion, and every professional inspection, the profession can generate value, the profession can win the respect of others, and the profession can survive. Why do lawyers or pilots look so handsome when people watch TV or movies? Because they are very professional. Therefore, as testers, we should constantly improve our professional quality, various test theories and professional skills, and study and study again at work or in our spare time, so as to effectively guide our work, enrich ourselves, and even throw out some esoteric technical terms in communication to shock others, and then look at others with admiration or confusion, making them feel helpless. In addition, it is very important that when there is a contradiction, testers must stick to their own positions and principles, argue with reason and not waver. Testing is sometimes the most easily sacrificed role. In order to catch up with the progress of the project, it is easy to cut off the test time. Even before the test is completed, it is forced to ship due to market or other reasons. At this time, it is a test for testers. At this time, it is also the time for us to quarrel. If the tiger doesn't show off, you will think it is Hello Kitty. Don't be afraid of quarreling, don't be afraid of contradictions, and strive for it. It is meaningless to give direct feedback to leading comrades at the next higher level, and stick to your own professional principles. If something really goes wrong, you are still responsible for it. Of course, don't be too surprised. If it is really the company's decision, then obey, but the questions that should be asked must be asked. Sometimes I always feel that the testers on duty are just like Wei Zhi, just admonishing them, thus creating the law of chastity. The third point: Wei Zhi should pay attention to the occasional compliment. Everyone likes to hear good words, and everyone likes to hear compliments. This is human nature. When communicating with developers, don't forget to boast occasionally. Even a simple sentence or two will have a good effect. This not only helps us to maintain a good relationship with developers, but also helps to maintain a good atmosphere of the team. Of course, everything should be moderate, enough is enough, and it is too disgusting, otherwise we will become courtiers. Finally, I have to say that maintaining a good personal relationship with developers is very helpful to my work, especially the development or testing process of the company is not particularly standardized, and many things still need the help of developers. How to maintain good interpersonal relationships depends on yourself. Everyone may have their own way. You can take advantage of formal communication occasions and pay attention to all kinds of abnormal headaches. We can drink together, play ball together and take a walk together.