People and projects are driven by goals. People tend to align their plans with the objectives set by management or other ‘stakeholders’, for example, to find fault or to confirm that the software works. For this reason is important define the objectives of testing clearly.
The mental approach to use during testing and revision phases is different from that used during software development.
The search for negative outcomes (failures) in a system, it requires curiosity, professional pessimism, critical eye, attention to detail, good communication with the development team and experience on which to base assumptions on errors (‘error guessing’).
There are several ways to improve communication and relationships between testers and other people involved:
- Start with an attitude of cooperation rather than argument, reminding everyone that the common goal is always to achieve a better quality of systems.
- Communicate the findings on the product in a neutral way, focusing on the facts and evidence without any critical attitude towards the person who developed the product.
- Try to understand how people feel, perceive the attitude of the tester and why they react in a certain way.
- Be sure that the other person has understood what the tester told him and vice versa, to avoid misunderstandings.