The latest update to your company’s product was successfully released in production just recently. Everyone is happy and glad because at least at the moment the project is over and done . But wait, (as the software tester) you still need to do a round of double-checks to make sure everything is working as it should and, with much gusto, you start working on it immediately, motivated with the thought of well-deserved rest after.
But you found an issue (or several issues) in the update and become frozen in your seat. You wonder why you never saw that (or those) before. You never doubted your testing as nothing short of flawless, you were confident in covering all the test cases before the release, but alas, for some reason, you missed one (or several) and it is deployed in production.
One software tester tells her boss that there are no issues in the update and keeps the bugs she found to herself because she’s scared of how the team might react with the news. Another software tester tells her boss that she found a bug in the update, doing the right thing, but starts to blame the programmer assigned to the specific feature because she’s afraid of being scolded for the mishap. Fear makes people do easy things in the short run.
Then another software tester tells her boss that there are issues in the update that she didn’t notice before, which she will fix as soon as possible with the help of the assigned developer. She makes her work life harder today in her decision but it helps her reputation and makes the product more stable in the long run.