What kind of tester is a good tester _ test

I've brought a number of development teams and test teams to talk about the good testers I have in mind. I hope it will help you in your future career.
1 Active work
How is your work attitude, is to evaluate a tester's most important aspect, a high level tester (refers to pure technical ability) without a good working attitude, in the Test team sometimes not only can not play a role in the test work, and sometimes hinder, and a willing to work tester, Even if his technical level is not high, people are not smart, but the work of his serious and responsible, you tell him things, he can seriously do, the tester will also play a great role in promoting the test. This is one of the main reasons why many companies are willing to let those who are just working to do the testing work. In addition, the tester's willingness to work can also have an impact on the development of a tester, for example, when one of my testers is free at work
Will learn qtp by himself, improve their technical level, so that in the next test, he can skillfully use this test tool to automate the measurement, not only improve the efficiency of work to reduce the strength of the job and create a better opportunity for themselves (because the use of QTP effect, was promoted to the test leader). Therefore, the effective use of working hours, active learning for a person to develop is very important. Another example is similar to one of my testers who, when their test task terminates abnormally, while other test group task is very busy, the initiative to participate in other groups of the test work, not to mention his technical level, this initiative to request the attitude of work to let him out from other people, attracted my attention, Nature will pay special attention to his work, and our every communication will let him learn a lot of new things.
2 serious, careful, not afraid of trouble
It must be said that the test work is a cumbersome work, if you are not serious, careful, not afraid of trouble, it is recommended that you do not enter this industry, otherwise, the final discomfort is certainly your own. There is a sentence: the details determine success or failure, this sentence is particularly applicable to testers. When the testers are doing the test requirements, each of the requirement points in the system requirements report written by the developer will be a few test requirements in the test requirements (you need to verify the normal situation, abnormal situation), sometimes it feels like a game of permutations and combinations, but there are so many permutations and combinations of this game, If you are not patient enough, it is easy to miss the test demand point, these omissions are often problematic (developers are also apt to forget to consider these places, causing problems), and the data entered in the test work is a very trivial matter. For example, a date legality test, it is easy to sum up three, 400 test data, you want all test work will be a number of what. And more frightening is that testing is not a one-off job and often needs to be done
Regression testing, all cumbersome work must be repeated, and in the repetition of the tester often because of fear of trouble, reduce the number of test cases, resulting in incomplete testing. So serious, careful, not afraid of trouble is a good test of the necessary quality requirements
2 Strong learning ability, good at summarizing
I was looking for a software engineering book when I went to work in 92. That's called a difficulty, when I first contacted the test in 97, there were few books on the test, which was a big hindrance to my level, but it wasn't an excuse for us to improve our level, and the tests we did in 97 were mainly functional tests, The first is the gorilla test, and then on the one hand from the professional books to search for testing data, on the other hand summed up our own experience, 1 years
In the future, we basically formed our own test process and methods, we have our own test plan writing methods, test case preparation specifications, test summary methods, the new testers can quickly improve their level, later testing tools to learn we are also using this method, in the QTP learning process, One of my subordinates, after learning for 3 months, basically mastered the use of QTP, but also summed up the use of QTP frequently encountered problems published to the
51testing, a lot of people think he is a technical Montana, in fact, he is only a 8 months of work, learning 3 months novice. Continuous learning of new technologies, and constantly summed up in the actual work encountered problems, solutions, and to organize their induction, is a tester to improve their technical level of the best way. There are two points to be explained. 1 as the testing work becomes more and more professional, the original low-level testers are increasingly unable to meet the needs of testing, testing
The use of tools, the updating of test theory, the application of new technologies require testers to continuously improve their level, 2 good testers not only to understand the test technology, the test system and the development environment and tools and system architecture must be very understanding to develop a reasonable test plan, That is, the Test manager should not understand the test technology, but also to understand the mainstream development technology, architecture and tools (although not to become an expert), all of these testers are constantly learning and summing up

3 Mastering Test theory
The development tool is changing, the test tool is changing, the system being tested is changing, everything is in the side, then as a tester is the most important to learn what, personally think that the test theory of learning, take my own example, I used to do pure software, but now exposed to a lot of hardware-related tests, such as mobile phone test , but no matter what you are testing the basic theory of the system is unchanged, first of all need developers to provide better requirements documentation. The outline design document, the detailed design document, the requirement document is the standard which we develop the test requirement, is also our judgment system existence question standard, but the outline design document, the detailed design document is we produce the test case the basis. Our basic testing methods, such as dividing equivalence classes, boundary value tests, and so on, require the support of these documents. Of course, each of the different types of testing, there is a special place, such as mobile phone testing requires you to have a certain understanding of communication theory (that is, the system environment), so the good tester must have the quantity to master the test theory. If you think your test theory is good, answer the question of how the performance test, the load test, and the stress test are different.

4 not idle talk, but charge in front
Some of my testers, always like to pay attention to me, but never consider how to implement, they like the word is, see how smart I can be the essence of the problem, the head I this staff is good (I used to do). I would like to tell you that such a person has actually fallen into a technical career misunderstanding, see the problem can show that you have a certain level, but how to solve the problem, how to implement the true embodiment of a person's level, the Chinese literati because of fear of beheading, produced a very terrible phenomenon is what light qingyi, and never to practice. This bad habit is now called Yangaoshoudi. Only when we solve practical problems can we discover that there are deficiencies in our solutions, what will create new problems, and thus constantly improve our work, a simple example, I have been using TD for a long time, but today I can still find TD some new features, and put these characteristics into my work, Improve my test management, so I personally think that good testers are always those who charge before the test, in the actual work is the best way to improve the functional ability

5 Handling of interpersonal relationships
The test work is a problem of the outbreak point, especially for those who development process is not standardized units, how to deal with good interpersonal relationships, is a good tester need to master skills, as a test lead and developers, testers, company leaders often face a short test time, continuous regression testing, Abnormal termination of tests, leadership criticism, developer responsibilities, testers ' complaints about durations, testing environments. How to resolve the contradictions, to deal with these problems is a measure of the quality of the test staff bad interpersonal management is not good, in fact, a major problem is misunderstanding, developers, the company leadership of the test workload misunderstanding is a major cause of these contradictions, so as a good tester, In addition to having some common interpersonal processes
Skills, but also a good propagandist, constantly will test methods, theory, workload of developers, superior leadership to preach, so that they have a correct understanding of the test work, only in this way to really deal with the test department and other staff of interpersonal relationships, is the unit of testing to a good direction.
6 familiar with development tools and platforms
Tired today, don't say much, do not understand the development platform is unable to do unit testing, but also can not do a good performance test
7 Mastering Test Tools
You don't have to talk about that.