Good test engineer should have quality
(This article is reproduced from Software Engineering Expert Network
Www.21cmm.com)
People are the most valuable resources in testing. There is no qualified, active test team, and testing cannot be achieved. However, there is a very common habit in the software development industry, which is to let those who have the least experience of experience, no efficiency developers or people who are not suitable for doing other jobs to do test work. This is definitely a light-shallow behavior. The skills needed for a system effective test are definitely less than the software development needs. In fact, the tester will get extremely wide experience, they will encounter many developers. I have encountered problems. 1. Communication capabilities A ideal tester must communicate with all people involved in testing, with technology (developers) and non-technical personnel (customers, management personnel) communication skills. It is necessary to talk to the user, and can talk to the developer, unfortunately, these two categories have no common language. The focus of the user's conversation must be placed in the system to handle what and cannot be handled. When talking to the developer, these live renections must be expressed in another way, and the members of the test team must be able to communicate equivalent to users and developers. 2, all personnel related to system development are in a state of concern and worried. User worry that the future uses a system that does not meet your requirements, developers are worried that he has to revisit the entire system due to incorrect system requirements, and the management department worried that the system suddenly crashed and made it a reputation. The tester must deal with each of the people, so members of the test team need to have enough understanding and sympathy for each of them, and this ability can reduce the conflicts and conflicts between testers and related personnel to the lowest level. . 3, technical ability, in general, developers hold a despise attitude toward those who do not understand technology. Once a member of the test team made a wrong concluding, then their credibility will be immediately promoted. A tester must understand the concepts of the test software system and will use those tools in the project. To do this, you need to have more programming experience, and the early development experience can help the software development process has a deeper understanding, from the correct evaluation tester from the perspective of developers, simplify the learning curve of automatic test tool programming. 4, self-confidence developers accuse the tester to have a common thing, the tester must have enough self-confidence to his own point of view. If you can do anything about yourself, you can't complete what more things. 5, diplomatic ability When you tell someone, he must use some diplomatic methods. Caracian experience and diplomatic techniques help maintain cooperative relationships with developers, and testers also need a certain diplomatic wrist when telling developers. If the method taken is too tough, for the tester, it is equivalent to "winning the war" in the future cooperation in the development department. 6, a sense of humor is in the case of a sophistry, a humorous criticism will be very helpful. 7, a strong memory an ideal tester should have the ability to mine similar errors that have been previously encountered from memory, this ability is impossible to measure the value in the test. Because many new problems are different from the problems we have found. 8. Patience some quality assurance work needs to be unbelievable. Sometimes you need to spend an amazing time to separate, identify and assign a mistake. This job is those who are unable to do. ⑨, the skeptics can be expected that developers will do their best to explain all the errors. The test must listen to everyone's instructions, but he must keep suspect until he has seen itself. Hey, self-supervising test work is easy to make you lazy. Only those who have self-supervision capabilities will work properly every day. 11. Insight a good test engineer has the viewpoint of "testing to destroy", capturing the ability of user views, strong quality pursuit, and paying attention to details. The high-risk zone of the application is determined to make limited testing for key links.
