This was a question recently raised on the forums.
Generally it depends on the environment within the project and how successful the project is going.
The tester could always be the bearer of bad news.. or the tester could always be the bearer of great news on items that have been discovered to ensure quality and success. Its the old the glass is half empty vs full mindset possibly coupled with a lack or wealth of SDLC experience.
I always see finding bugs and issues as a positive, because 1. we are able to prioritise and address them if needed, and 2. it means less issues further down the SDLC resulting in a ‘cheaper’ and ‘easier path’ to ensuring quality and early risk assessment.
Teams may see issue/bug discovery as a negative if they are inexperienced or suffering from a bad project experience/support/burnout etc. Generally speaking they should see it as a positive when finding and addressing issues in project mode, rather than after the project has been completed when it will cost exponentially more in time and money to address those issues. (if at all possible).
What should a tester do to avoid being the bearer of bad news? Explain that its a good thing that you are able to address those issues early, be positive about the process and be clear that issues will always be found, its neither good or bad but a fact of software/system development, however its infact a bonus having to address them now than later on. Note finding a bug may not necessarily mean that they get fixed right away, but your job as a tester is to get those issues assessed right away for priority and severity.
Happy testing and be positive with your discoveries.
