Eighth week of software testing--the feelings and suggestions of the people in the industry

Summed up the experience of the Test practitioners and suggestions

Personal deepest feeling is: engage in any work in the software industry, good prospects need solid, reliable programming ability as a support, lack of this basic has important skills, it is difficult to achieve real career development.

The skills required are as follows:

Common skills:
1. Basic computer knowledge (operating system, database, communication protocol principle, familiar with at least one programming language)
2. Basic Software Testing knowledge (various test theory, test methodology, test case writing, defect definition standard, software quality evaluation)
3. Simple Project Management Knowledge

Product and System cognition:
1. Familiar with the product features, can be described in the product documentation in the UC into TC, the most basic
2. Familiar with some hidden requirements or functions of the product under test (Advanced ability in business)
For example, to pay the company a new payment channel, familiar with the business of the tester should be able to foresee that the upgrade may be the previous interface, system accounts, various types of reports, such as the impact of various modules, to be included in the test category.
You know, many times, even product managers who access these channels do not necessarily list these visible effects in PRD or UC, which requires experience and responsibility.

Character on:
1. Have the properties of the cow-skin sugar is good, the more "no face" the better
Test engineers, in many companies, and research and development are in the business of opposing attributes (although from a macro point of view, are to improve software quality services). The more bugs a test engineer submits, the worse the quality of the research engineer's work, the greater the amount of rework required, and even the impact on performance, so the test engineer can easily offend the research and development department.
A test engineer who can stick to the principle (such as a level 3 bug must be changed), and be able to pull down the face and have a good relationship with an unpleasant research engineer, will play a key role in the quality of the project. In the final analysis, and can do things (find bugs and urge to change), but also will be a man (the face, the absolute return to the end, to maximize the elimination of inter-departmental contradictions) test engineers, is very rare.

2. It's best to have a whimsical attribute
This imaginative achievement here is a bad word. In the team I have brought, there is really such a wonderful ... It's a natural gift to find bugs in incredible ways.

3. Will be "lazy" for the better
The lazy here is not to go to work microblogging chat, but can use known resources to the tedious test work to optimize the classmate.

Feel the following:

1. The ability to write code is still very high, and if you want to test well, you need to understand why this problem occurs.

2. Testers and developers are becoming less differentiated in large companies, meaning that testing is no easier than other jobs.

3. The software testing industry is essential, but the prospects are not as broad as those who are genuinely engaged in technology. You may consider entering a large company or a formal testing institution.

Eighth week of software testing--the feelings and suggestions of the people in the industry