Testing Software - the right mindset for better results
This doesn’t mean that the software tester trusts no one. It’s perfectly okay to trust the developers, it’s just not okay to trust the product. When it comes to software testing, skepticism reigns.
Software is developed to solve problems or facilitate actions. Developers and designers must approach development and design with the assumption that these goals can be reached. They are required to be optimistic. While the tester, on the other hand, is required to be pessimistic. A successful software tester is often considered nitpicking and anal-retentive by his or her colleagues. It’s the price you pay for being a good tester.
There are all sorts of reasons why a tester must be critical and skeptical. For example; the pressure to complete a project can cause developers to overlook sometimes ambiguous results. If the tester doesn't sniff out these potential problems, they will end up in the end user’s lap. We are all familiar with horror stories of what happens when software is put on the market prematurely.
So, it's important to work with developers in a friendly and open-handed manner. There is nothing wrong with honest criticism and no one should take offense. We are all on the same team. However, it is vitally important to make certain that the software reaches the market as clean and functional as possible. The reputation of everyone involved is at stake, as well as the future profitability of the company.
It's better to find the bugs in testing, than to fix a crash in the field.