What kind of role does a tester play in a software test? _ Software Testing

In the work often encounter products on the line after the bug, the first to be blamed was the tester, "Why did the test not find the problem", which is countless in real life, perhaps they have the tester as "Super Magician", the test of the hands of the things are flawless, This is the role of positioning issues, when the role of the positioning of their own, in the negotiation of the role of the content, there will be in any case when there are problems in the first to establish the basis for their own expectations.

First, good at making questions

Testers do not ask questions during the requirements analysis or during the testing process, is not unable to test, just can not better test, ask the question is the test personnel to the project to play the foundation, does not ask the question, the test does not have the goal, the idea is not broad, the analysis is not thorough, is only the mechanical test intrinsic function, listens to Ali a colleague to have spoken , they will be published in any product test report must reflect the project's risk point is what, if do not think not analysis, the risk point is not easy to raise, then the test meaning can be discounted. (For more highlights, please stamp: recommended.) The test engineer is promoted to the test supervisor's advanced process.

Second, with the development of a high degree of cooperation

Providing support for programmers is a key part of the tester's mission, when the programmer is still writing code or writing to complete the test, the tester can provide the test tools for the developer to quickly verify the use when necessary, and after the program is delivered, should start the test immediately (of course, the preliminary test preparation needs to be sufficient), as far as possible to establish the shortest , the fastest feedback loop. While the programmer is still struggling to figure out how to solve the bug, the test has begun to look for more procedural questions, ideally in the form of a programmer, rather than a tester, that is the bottleneck of the project, reducing the potential risk of the project, in order to modify bugs. And here you can add a bit of the tester's role, that is, the bug positioning problem, not only to see the problem, need to delve into the nature of the problem, a layer of open its face, for developers to save time, shorten the bug life cycle.

Third, recognize the key

Testers do not find all the problems, and the tester's task is to identify and report important procedural issues. So suppose, in order to discover all the bugs in the program, testers have to check all the possible problems, to observe these places under different conditions that are likely to occur, and a very reliable way to recognize all types of errors when they occur, so if a tester can do that, Either this product is particularly simple, or the tester's imagination is limited. When we know and admit that we can't do everything, testers have to choose how to take advantage of their effective time.

Experience Summary: Quickly identify critical procedural issues.

1, first test the change of the part, and then return to the old function, identify the risk of new changes;

2, first test the core part, that is, the key and common functions;

3, first test the function, and then test the reliability, consider all kinds of abnormal scenes;

4, with the ability to identify the risk level of the bug;

... wait a minute.

Of course, it requires testers to have absolute familiarity with the product, more quickly to find the problem.

Iv. testing does not guarantee quality

Testers are not quality guards, testing will not improve quality, and will not reduce quality, good quality code is there, quality from the people who build the product, sounds incredible, but this is the heavy burden they have to bear, the other part of the tester's mission is to help them deal with the real burden. But if testers think they are the only people in the project team who care about delivering a good product, they can't do it well, stating that testers don't recognize their role, that testers ' tests and bug reports provide information that promotes quality assurance, and that the team is ultimately assured of quality. So testers should never be gatekeeper, otherwise it is irresponsible for the whole product. When you take full responsibility for the quality of the product, the rest of the team can relax and even relax, and if the problem is missed, the other members take it for granted, why you didn't find the problem, and the accompanying questions about your workload.

Experience Summary: Quality is required to be shared by all role participants in the team.

Original Author: dsy851009

Original link: http://blog.jobbole.com/106915/