IT practitioners have always been in dire straits, and they are most afraid of new demands or changes in products. At work, this is often the case. Seeing that the quality of the test code is not ideal, the launch time may be delayed.
Manager asked: When will it be online?
The developer said: I don't know, let's see when the test will be finished.
The test said: I don't know, let's see when the development can be changed.
So a group of people in a trance, I push you, you push me. When will it be online, God knows.
Do you think the manager will accept such an answer? It's strange, what is the overall plan for, and you have to go online on time even if you work overtime and have kidney deficiency. So the development and testing started to move bricks after eating the takeaway.
In all fairness, the work of development and testing complement each other, and they have only one purpose: to ensure software quality. No matter what is the reason for the delay in the release of the version, it is always the team's fault.
No matter how dev and test fall in love, the whole software project has to be done. In the process of development and testing, it is inevitable to complain about each other, and the feelings will change.
【1】From falling in love to killing each other
Practitioners who have just entered the IT industry must have heard the legend of programmers. As for what kind of legend, they will definitely understand the relationship between development and testing. Every development and testing employee is friendly at the beginning, but as the project progresses, development and testing gradually become antagonistic due to the urgency of development time and testing time or bug fixes.
There is a blog post on the CSDN website that describes the relationship between development and testing, which lists several scenarios:
Developers say that testing is a no-brainer, and customers simply can't use the software the way they do
Tests say that problems always arise under seemingly extreme conditions, and users are always inadvertently exposed to seemingly extreme and impossible conditions
Developers say that testing spends more energy in abnormal situations than testing the main process, and I don't know the priorities
The test said that development never considers the feeling of testing, and it is thrown to us without even testing.
The development said , I have tested it, what do the testers do?
The test said, if you don't test such an obvious problem, use our test as a trash can.
……
In fact, there are many similar problems in the work, so who is at fault, everyone is justified, but the perspective of development and testing is different. It is inevitable to argue over a certain issue at work, but if you really allow these quarrels to develop and deal with things and people, the relationship between development and testing will gradually become antagonistic.
There are even leaders who are happy to see the development and testing quarrel, and take the initiative to promote the antagonistic relationship between the development team and the testing team. This is the case with the company I worked for. At first, the development team and the test team were daily complaining but friendly friends until a new leader arrived. The first fire of the new officer's appointment is to develop and test: how is the relationship between testing and development so harmonious?
Leaders want to quarrel between development and testing, and the more quarrel the better, so as to improve the test efficiency and bug fix rate.
Since then, there have been more and more quarrels between development and testing, ranging from bugs being fixed or not being able to be repaired to developing sarcasm tests that do not understand technology, from slow development progress to compression of testing time to testing delays and complaining about poor development quality, and sometimes even personal attacks. As a result, development and testing entered the Cold War period, with zero communication in daily work and daily challenges in order to defeat each other.
I don't know if this work mode really improves the software quality, but the office environment and work mood are depressing. Whether it's spontaneous development and testing, or leadership-driven adversarial relationships, it's an unhealthy work environment. Competition does exist, but there are also partnerships. Development and testing should take work seriously, but not people too seriously.
There are oppositions due to the working relationship between development and testing, and there are couples due to mutual complaints between development and testing.
【2】From killing each other to falling in love
My friend Dapan is a straight IT man who writes code and complains every day.
Although I am a tester, he often complains about testing in front of me. Yes, as a good friend, he complained directly in front of me, showing what a straight man of steel he is...
I admit that some of his complaints exist, but some of them disagree:
Tests always test some situations that are impossible in the actual formal environment, or even misuse
When I test the deployment environment, I always call me, and I don’t read the deployment documents carefully, so why do I always ask to develop and write the deployment documents
The test always mentions the Zen Tao without making it clear. Some of them are not fundamental bugs, but they are clearly designed that way.
The test always asks us to develop the problem of the requirements
The test technology is too poor, the positioning is not accurate
I thought that ranting like Dapan must be very annoying about testing. But the fact is that I finally fell in love with the test. And it's the test Xiaomin who he often complains about. When I asked the reason, I found out that Xiaomin also often scolded him, and when he slapped him, he became emotional. How did Xiaomin hit him:
Development is always not based on requirements documentation, always free to play
The documentation written by the developer is unclear, and no one can understand it except himself
The common problems must be raised one by one, and the development will change them all, otherwise only the raised one will be changed.
Development always only focuses on normal processes, and abnormal process operations are not considered at all
Although it is not as good as the development technology, the test also knows that some bugs are easy to solve, why is the development not solved
Dapan said that when he was complaining about technical problems, he mentioned python for some reason. Dapan just solved the problem that Xiaomin encountered in automated testing. From then on, Xiaomin looked at Da Pan with star eyes, and Da Pan looked at Xiaomin with shy eyes, so the two of them were shy together. So Da Pan and Xiaomin became love complaints, and they sprinkled dog food silently in the office.
This combination of development and testing is a bit dreamy, and it is not out of the way that girls adore boys and boys help girls. However, the changes in emotions at work are developed on the basis of not affecting the work. Even if they are in love, they still treat bugs seriously and selflessly in the development process and testing process.
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.
If you have any questions, welcome to add QQ group test entry God 755431660 to learn together
~