How to become a qualified test engineer

     Some time ago and a few test talking with friends, when it comes to the first half of 2006 to test community news, I think the biggest news than report a testing industry Zhaopin website now.

    The report pointed out that "the current test will not be more than 50,000 employees, qualified testers will not be more than 30,000, while the work of more than five years will not be more than 10,000," to say nothing of whether the data is accurate (according to my experience, it should be pretty close). Single Here to talk about what constitutes a qualified test engineer, how to become a qualified test engineer.

Let me talk about what constitutes a qualified test engineer.

A test engineer should have the quality I think in many book about software testing have already been cited, and will not repeat here, but the biggest difference between a qualifying test engineers and test engineers Where? Nothing more than just to test ideas. Qualification is that he received after testing task first thing is to do and not do. Qualification is that he will always be his own ideas throughout the test, including test design, test execution, test analysis.

Many people will say testing idea is a hollow thing, and I have written or said that too many examples to prove it, here is recommended only qualified test engineers who want to go read a book club, its name is <think in java>, in my eyes, it is not a book about technology, but it also does not apply only to developers.

Then talk about how we can become a qualified test engineer.

There is not a joke that a certain company sweeping aunt can do software testing, certain company janitor uncle can do software testing. This shows that people are embarrassed misunderstanding of software testing and test engineers. In fact, not just any person can become a test engineer, test engineer is not really any can become a qualified test engineer, in order to become a qualified test engineer, you must still flesh and blood of thinking. Technology can not learn, can not learn ideas, ideas that need practice.

So I suggest that you:

1. test every six months to read a book (now test books also increased, although many of them are East West copy copy, capacity enough, then read the English original, the basic translation can not fully understand the author's ideas, others foreigners test development than my door a few more years yet)

2. test every six months to learn a technology (IT industry is changing rapidly, testing technology also, every year new testing technologies emerge, we do not want to have a grasp of every emerging technology, only hope that every testers I have engaged in this industry to fully understand and are familiar with, because your current and future projects in the test, you have to choose the most appropriate and effective testing techniques in this project, even if you do not know the selected object, then talk about how to select , they talk about how appropriate it?)

3. every six months to learn an IT technology (IT here in the technical scope is broader, testers do you want to learn more knowledge, such as performance testing you do, you need to understand the operating system, you need to know about software architecture, you need to understand the low-level implementation, you need to know about middleware, you need to know about the database, you need to understand their configuration and implementation, you also need to understand the hardware, to understand the network, understand memory management, understand the disk I / O and so on principle)

4. To learn to think (the tester should learn to think before the test, the test thinking, thinking after the test, the results of thinking to be recorded, no one dare say he is a genius, you can remember everything. Like a good then do it, to validate it, if not, it returns to rethink, and then do it, the only way you will do better.)

5. To attach importance to the test design (a developer has said he proficient in JAVA, proficient in C, I and then he said, that give you 10 or 20 years, you use your mastery of JAVA to write a WINDOWS operation can be replaced system. since then, he does not say so, because he knew even gave his life, which for him is a dream. test it not, no matter how high you test the technology, you can not test better, pay attention to test the design of it, this is the the key test.)

6. Multi-testing and peer exchange (in a closed circle, or in a company, you think you are a master of the test, when one day you get out of this closed circle, you discovered, there is day, maybe I'll spare you a bundle may puzzles some tests counterparts played down the sentence that you can solve the test is the same test idea is the same, and more to do some more, before they can see their own shortcomings.)

I advocate testing techniques, it is believed, respect from strength! So I hope more testers can test respected peers, can be respected developers, can be respected enterprises.

At the same time I thought more respect for test, so I believe, after the software industry more standardized, enterprise requirements for test engineers must test the idea first, experience second, and the third row can only test technology.