Do software testing need to have what skills?

1, software testing basics:

Test plan preparation, design test cases, write test reports, write BUG report form, tracking BUG repair, but also need to have good communication skills, as well as a variety of test phases of the test methodology used, unit testing, functional testing, integration testing, system testing, etc., CMMI / ISO9001

2, the use of various testing tools:

We work in the test in order to improve the efficiency of the process will use a lot of tools, QTP, LR, QC, TD, Bugfree, VSS, SVN and other tools, although the tool is not omnipotent, but the tool for us to improve the efficiency of the work, so we can not be a tool as a god as the same as viewed, but it must be able to use skillfully!

3, operating system-related knowledge:

Windows, linux, uinx these must be used, and not just simple operations, general service management, registry editing, command line operations need to be able to imagine that even an apache service will not be able to install and configure the person who can imagine that you can do a good job based on the apache environment testing work. apache environment based on the test work, what? Do not know how to view the disk pressure, IO data. windows linux have provided their own tools can be used to view these data, perfmon, top, and so on.

4, database knowledge:

Now Oracle's DBA treatment than the general treatment of developers is still high enough to know the importance of the database in the enterprise, as a tester, although you do not need to have the ability of the DBA, but the basic database operations you have to be able to, whether it's Oracle, DB2, MSsql or mysql minimum should be familiar with the use of one or two of them. should be familiar with the use of one or two of them.

5, computer hardware knowledge:

Friends who have done performance testing know that in the process of performance testing hardware performance is a very important indicator, CPU, memory, IO, bandwidth, etc., if you are doing hardware testing. Then there is even less to say. Switches, routers, firewalls, these devices need to have an understanding.

6, network protocols:

If you still know what is different between TCP and UDP, please hurry to add some knowledge, the Internet era, everything is transmitted through the network, the common protocols must be understood, once interviewed a test engineer to do 2 years of testing actually do not know what protocols they use to test the software, such a person is your words you dare to recruit?

7, the development of the language that code writing ability:

While you can not write code to do testing, but if you want to do more than senior test engineers, then the code writing ability is a must, if you do not write code, then you can not become a senior test. Part of a senior test engineer's job is to write test tools. Although the test also need to write code, but do not need to be as proficient as the development of a language, but the test but need to understand a lot of development languages (for a simple example: you are now in the project from the C + + + language, 2 years later you changed jobs, the new company's development language is java or VB or something) so in the development of the language of the test needs to be more broadly learning.

8, industry knowledge:

Industry knowledge is written in the last because the first 7 we can learn to master, but only industry knowledge can only be accumulated through work experience, do not say you go to read a few books to know the communications industry, the medical industry, or the aerospace industry, do you think that in the books above can learn?

Because of the special nature of the industry knowledge, it is recommended that friends do not frequently jump from job to job, the accumulation of experience is the need for time to precipitate.

9, with a certain aesthetic concept:

This is a bit awkward to say, simply put, whether it is the development activities or testing activities, the final goal is to bring the product to the market, and get the user's approval. So if the product in the requirements analysis stage has deviated from the user's course, then even if the testing and development do a good job this project is also the same will fail. So if you are lucky enough to be able to participate in the requirements review, please don't be stingy with your comments.

10, please do not forget to always learn:

This point I believe we should be able to understand so do not have to write anything: just this point "do not learn will fall behind"

Summary: said so many skills or that is to say that the need to master the technology, if you do not have a heart to find the beauty of defects. mentality, there is no one to improve the quality of the premise to put into the work, then even if you do well in other is only one of thousands of software testing practitioners. Most of the testing activities for the discovery of defects, and after the discovery of defects after the work is particularly important: how to find defects from to improve quality.