Glenford Myers in 1979 by testing a different way: the purpose of testing is to find defects. He used this definition because it motivates people. Consolidating on the negative and trying to break the product lead to finding many more serious defects than the simple test: "whether the product"
Most people do as they say. If they are told to find as many defects, they will attempt to do so. If they are told to do the job (and explicitly or implicitly suggest that defects in slow progress), they will try not to find defects or miss many of them.
Thus, the first rule is to clearly define the purpose of testing, and make this goal very clear to people. There is also another problem for all the work, not just testing: the world is developing, especially in the software. New techniques, methods and tools become available or are already being used in the design. Software products are increasingly integrated with each other and becoming more and more complex. The focus is shifting requirements, such as increased focus is security, interoperability and ease of use. This leads to changes in the requirements for testing. Thus, the tester should continually strive to learn more.
Another problem is the human way of thinking. Some people are willing to take the information they have visible or regulations that are being forced to perform. Others are critical, understand and ask. As one of the objectives of testing is to find problems and defects, the type of thinking that does not take anything without asking, check more details, get more information or deliberation leads to better testing.
Part of the tester’s task – the message about the issues. It is not easy. Most of the literature read by testers, only describes the defect management, ie the life cycle of reporting, prioritizing and processing. But this is only a "normal job". In fact, the work is much more extensive. This can be compared with the task of frustrated customers calling the help desk vendor: to describe the problem so that the other party accepted it as so important to take action. This means collecting more information about the problem and thinking about how the "submit" bug report to the responsible person.
Finally, the tester has some rights. We should not just test something thrown us out of the wall. If the information we need is not available or very poorly tested product, the testing of the product in any case would mean a waste of time. Should be the specific input criteria for testing, a "Bill of Rights Tester» (Gilb 2003).