1 , I want others are thinking.
From the user point of view to consider the issue, they regard themselves as end users how to use this software. Needless to say this, we should be able to understand, for example, usually referred to recommendations of bug, largely from user perception;
2 , reading bug.
There is a "language" is: familiar bug thousands of times, looking for bug is not difficult! In fact, it just makes sense, from someone else's bug you had to be able to capture others how to think, how to find this bug does, exercise its own breadth of thinking;
3 , analyze your bug.
Bug tracking solution for their own final submission, why the development was out of this bug, the bug will not think of the other places may be out of the question? If the next time you encounter a similar function when the problem will not occur play a good reference; another problem experienced by much, maybe when you find problems when directly think of a developer program which part of a problem, it can save developers time to some extent, improve the efficiency of solving the bug;
4 , understand the overall architecture of your test function.
Whether you test which part of the function, you'd better get to know the source of this design feature, interactions with other modules, for example here, I've been through: the blue flood background server to do the test when, where demand is a log analysis and statistics pv amount, I tested the program is the essential function of statistical directly after storage is over, but then there is a problem is that when the amount pv is 0 when he does not affect the storage, so I did not consider, but happens to have individual front-end department need to use this data and display it on the page, the question is, their code does not circumvent the divisor is zero, the time display on the error, of course, this should be their aversion but there's just the code maintenance phase, new developers do not want to move the old code, and the changes will also affect other functions of the program, the heavy workload, the ultimate solution is to roll back the program on our side, removing data of 0;
5 , analysis needs.
The best start to the participation of the entire demand finalized, the most direct way is to participate in the discussion meeting demand, because you'll hear at the meeting they discussed why this needs to achieve, to achieve what the code needs to be changed so forth, so that you know more about the inner workings of the entire project will help you write test points.
6 , more communication.
In fact, multi-purpose communication is nothing more than a better understanding of the needs, including communication with product developers and staff, at the same time can also increase product development and relationships with people, which is a school door, smooth communication, and can do more with less .
7 , a sense of crisis and learning innovation.
Many do the test for a long time people have an idea: I could have been doing this test it has been little bit? We all know the answer is no, because you can do most of the recent graduates can do, how it should not be eliminated to enhance their own time, when it is, from the work itself to think about, whether you repeat these labor there are ways to not repeat this, is to think about how the liberation of labor, then for testing, the first thought is the use of automation, which automated mode selection, you simply need to own needs, you can use your own test scripts, such as shell, even python java, you can also use open source automation tools, there are also a lot of functional tests such as QTP, performance testing loadrunner and so on, do not be afraid to use these tools, if you have the needs of the target, not to learn difficult; the last time any professional staff to maintain a positive learning attitude is very important, he decided in the end you can go far!