Bugs that disrupt the line-of-business can easily rake in
million-dollar losses per downtime day.
Bugs that compromise data integrity can cause irreparable damage to
Bugs that compromise security can allow targeted individuals to
commandeer certain corporate assets. They could also choose to
compromise data integrity along the way.
But most of the bugs are just nuisance, like flies. They just slow
down users a tiny little bit. One thousandth of their time - which accumulates.
For each bug that cause massive disruption, there are 10x more bugs
each can cause minor disruptions.
For each bug that cause minor disruptions, there are 10x more bugs
that lose data silently for months.
For each bug that lose data silently, there are 10x more bugs each
annoying users and slowing down things a little bit.
(The effects on this list are, as you have guessed, accumulative.)
If you have ever been impacted by a show-stopper bug one day, take
Not that I approve of the quoted text.
High-impact bugs are like freak accidents. Thousands of hours of manual testing will reveal and fix lots of little UI bugs, but it has to be combined with careful coding and code-level testing etc. to reduce the occurence of rare but high-impact freak accidents.
Can a certified software tester ensure that sufficient resources are devoted to each and every level of testing? Can a certified software tester deeply understands every level of testing (despite passing the certification exam) and able to spot out glaring inadequacies in test implementation (administration) - not of the paperwork kind? Can a certified software tester withstand managerial pressure to "make a trade-off" between release date and testing?
If you have a track record of success, it will speak for you. kudos.
This is not a rant against certificates. In fact, it is a great communication tool between the test lead and the manager, if they are both certified. This basically eliminates miscommunications mishaps.