Lead: testing practitioners, dealing with the most is the development, and the relationship between testing and development known as 'predators' in the industry.
That as a test engineer, you better know how to deal with the relationship between the development of it? In fact, for this 'hostile' relations, we are not difficult to understand.
Development is the manufacturer of the product, the product is equivalent to his 'children', and the test job is to find the "child" who's wrong. I believe that no child is like his mother picked the wrong variety, then let yourself go correction remodeling. So, the natural enemy of human nature property, development and testing indeed inevitable. So we often see such a conference room or a number of small scenes and dialogue among the various tea companies:
Several workers complained test developed by various acts:
A: xx Development Every time we came to a bug let me reproduce, obviously I bug in the procedure is described as very clear, he will not look at the operation!
B: xx too dependent on the development of the test, the same bug propose a change one, the same type of bug in the relevant modules together can not modify it?
C: encountered do not want to fix the bug, he said he is a good local, or test version does not question, or else say so users will not operate without repair, anyway, is not trying to repair the bug!
D: Let me open a bug to develop clear data, clear cache, or restart the phone, put the bug entire San Liangxia gone, reproduction does not come out, say, see, can not reproduce, do not fix it!
E: I opened a bug, obviously beginning to stabilize reproduce, then development has been placed there regardless, so after a period of time, my environment is destroyed, or test version upgrade, let me reproduce this bug a waste of time to re-take the environment is not to say, often no longer reproduce the bug, and then he said it could not reproduce the bug will not fix ...
F: Completion of the development of this bug report no unit testing, and bug Description Remarks no, do not say clearly root causes and effects module, how I do regression testing ah! ......
Testing for development of all sorts of acts, and cry complain Road, endless.
Of course, the development of the attitude of the test better there, you can often hear the same developers get together to complain testers:
A: xx often prescribe such a small bug, also requires the development of a total change, the impact is not large, but also time-consuming, testing and project management did not know the estimated risk ah?
B: These are obviously the client bug, our server is assigned to several meanings? Testing will not be his first positioning about it? This operational capacity have not!
C: often spend a lot of time to troubleshoot and locate bug, and eventually even found to be invalid bug, test in the end there is no clear demand? Simply a waste of everyone's time!
D: Major's obviously a bug, gave me a report into the critical level, also causing me to be leaders urge overtime, own a little more cautious given the level of bug not it?
E: xx test always been asking bug causes and solutions, testing and do not understand the code, say do not understand, I have to explain a waste of time!
F: Test day out a bunch of processes and documentation, provided that the offer to develop, develop writing code can there be so much time! ......
Looking at these words believe as a test engineer you must have felt no stranger. Because the position is not the same, not the same duties, the emergence of such differences and conflicts is understandable. However, if you work in such an atmosphere every day, we need to put in some effort every day to talk to the development of wits, not only affect our daily mood, and certainly also affect the efficiency of our work.
So, as a test engineer, in the end what can we do to improve this hostile relationship? Or we may be trying to harmonious working atmosphere from what areas?
** ** direction of the test can be hard
1. I think the test engineer should improve their core business capabilities, allowing developers to pick out problems, thereby creating trust in you even admiration.
On this point I have personal experience, so deep. I used to work for about two years, switched to a foreign company to be a senior test engineer. When arrived in the company involved in the project are always extra careful, but also through the open bug will be sent out repeatedly confirmed. But even so, with the contradictory development of the company's still not spared. At that time the company's development boss is a particularly strong person, strong sound great momentum, a kind of person can speak of scared senseless. I had opened a bug, in my environment following repeatedly confirmed, it is capable of stable reproducible serious bug, so I tagged for critical level, and assigned to development. The development of the corresponding module positioned generally a bit, not reproduced to. Then this development boss, come on aggressive testing office, airs with me test manager, he said:
'How do you test the open bug is not a bug they have not thoroughly understand ah? Now the development environment is OK, the problem is certainly question your test environment or method of operation! Next time figuring out recurrence bug, do not waste time developing ... '
These words are not at all rude, directed the whole point to the test here, do not leave any room.
My heart was certainly very angry, but I have no direct stand up and argue with him, because I know, you need to master the theory must be valid evidence that he can have confidence, or is irrational, there is no chance of winning.
So, I successfully reproduced to this problem in their own environment again, and then go find a developer to help him set up the same environment, he told a stable reproduction steps to reproduce the bug in his environment, and help develop the positioning problem out, they only need to modify the corresponding code on it.
The whole thing, I did not go to fight, not to theory, with their professional services capabilities, make them convinced.
After this thing from the entire development team for my attitude significantly improved, not only no longer airs pointing and questioning my work, but also to modify bug state (non-repair status) will be the first time confirm with me before making changes after obtaining permission of the respective state.
I have a lot of work carried out smoothly.
Therefore, to avoid falling into mouth, please do yourself. Test to do their most important prerequisite is the need to improve their operational capacity:
◆ one hand to adequately familiar with the product, understand the logic and implementation of products, on this basis, will not only improve your testing skills and work efficiency, but also in the development of question time, but also have a solid product backed by knowledge, there is sufficient justification to do emboldened, might have a theory of victory;
◆ On the other hand, we must regulate the output of their work. For example, to ensure the quality of various test documentation (test plan, test cases and test reports, etc.), it can stand the development, review of various departments of products; such as to ensure the quality of the output of the bug, write a clear description of the bug and steps, the bug severity level positioning accuracy, as well as positioning log and complete the scene shots, not to leave room for the development prick.
Improve the quality of their work before they can use the same standard to the requirements of the development, in order to hold the position in the test, but also earning respect.
2. Second, testers also need to improve their technical capabilities, including testing of skills, and technical skills and knowledge related to testing.
Also to share a true story.
I had a colleague, but also to do the test, because it is the black box, she did not know the code. In the course of project work, she met a very pleasant development cooperation, whenever they want more deeply familiar with the product's features and business logic to achieve when developing advice, he was very uncooperative. Two men quarreled before, had also hate each other, or both, had led mediation, but the situation will not improve.
There is no way, in order to ensure their testing tasks can be completed on time and amount, she could only forced himself to read the product's source code.
Although at first I can not read, but she insisted, while looking for information, consultation over others, and finally the code of this product related modules are familiar.
In the subsequent testing process, meet bug, she can accurately locate defects out of their own that piece of code.
Since then, never heard her quarrel with that development, because she has become the person most familiar with the product, whether realize the function, or code logic, she knows quite well.
Technology in hand, without asking people.
Therefore, test engineers can be properly targeted to improve their technological capabilities.
That increase from what it?
◆ First, be sure to test the skills, test procedures and test methods to master a variety of work is the basis of the test, so this is a must to master;
◆ second, second, it is best to be familiar with at least one language, whether it is java, C ++, or other scripting language python, perl and shell, of which 1-2 can grasp. With the foundation, the test can achieve a deeper understanding of the language products, but also be more clearly understood that a module bug often occur, the product can be more fully tested;
◆ Third, at least to master the use of a database, such as SQL operation, and can be queried using JOIN, or HAVING usage, the tester can not do without database management and operations, to master the skills in this area, it no longer have to rely on development, reduce their passivity;
◆ fourth, also need to be familiar with system-related operations, such as installation, configuration, management, Linux system for common operations need to be familiar commands, to be able to install and configure the software under Linux.
In short, to improve their technological capabilities in all aspects, to be able to give full play to their initiative at work, not overly dependent on the development in order to improve their expertise in the development of the eyes, to win equal treatment on both sides.
3. In addition, test engineers have to improve their emotional intelligence, enhance their communication skills, know how to stand in the perspective of the development of thinking, learn to respect the developers.
I believe we all know, no matter what the scenario, effective communication have always makes things done more efficiently, deal with the relationship between the test with the development as well.
As testers, we insist on the angle and position in addition to their own tests, but also on empathy, learn to stand angle look at the problem developed.
In fact, many conflicts are derived from everyone needs to understand is not the same result, so when the time testing and development of a bug with different views, not the first to deny him a very tough, trying to explain why he needs to understand there are deficiencies place. Some may find tenable argument, from the user perspective, from safety considerations, or from the ease of use and friendliness of view, to convince developers tested point of view, rather than imposing their own views to them;
In addition, usually spare time we can also communicate, have the opportunity to organize some activities for the development and testing to familiarize yourself with, like this very often face the familiar people, at the time against the other's point of view will be more likely to consider each other's feelings as long as the atmosphere is not the opposition, a lot of things we can talk things over.
These communication skills are reflected in a person's emotional intelligence, which is why many companies hiring testers are required when good communication and expression, the expression of high emotional intelligence and communication methods, can make our work environment a little less sharp, more gentle.
4. Finally, at the corporate level, the best there is a sound management processes, through process control to regulate the development and testing work department, the same can largely reduce the incidence of conflict .
Quality assurance has never been more than just duties testers, but requires the whole team together. So establish and improve the process, can help improve the quality of the product.
I had a company work, director of the test department has been working on various development and implementation of management processes, such as using the process to regulate the output template test documentation, and test bug to open a template, you can improve the quality of the work test;
As well as with specification development process to unit test report stating bug fixes and root causes that can help verify the bug testing and regression testing;
The same process used to regulate the bug of process development process, such as before closing the bug must send an email with the confirmation test, to avoid the bug has not been confirmed to be closed without authorization caused contradictions and conflicts;
Another example is normative project code review and code the final stage of the ice, we can improve the code quality and reduce the risk of publishing the final stages of a serious regression problems ......
The implementation of various processes, it might seem tedious, but strictly enforced, and indeed can solve many substantive issues, to help alleviate a lot of sharp conflict between development and testing.
**to sum up**
All in all, although there is a natural 'hostile' relationship between development and testing, but as testers to establish their own position, clearly know whether development and testing, the ultimate goal is to make the project a high-quality, time-sensitive completed. Development and testing lie at the root and only cooperation can accomplish a project.
So whether development or testing, we can not do without each other, test engineers to develop not work prick finding fault.
But also more than developers accessories staff, need to improve their own at the same time, rational process and look at the relationship and development, and jointly create a good working atmosphere pleasant.