I'm not familiar with the examples you cite, but as a seasoned Tester I urge you to look beyond the obvious to the root cause of those and any other examples your are presented with. I can't think of a project I've been on where serious bugs for system failures were not caused by some other serious problem upstream of dev. When you're working with competent devs, you'll find most problems are introduced due to poor requirements, miscommunications and unrealistic expectations filtering down from management, and lack of resources applied to test infrastructure and testing. Management should be held accountable for all these things, but instead they scapegoat testers and developers to CYA.
Slashdot Mirror
I'm not familiar with the examples you cite, but as a seasoned Tester I urge you to look beyond the obvious to the root cause of those and any other examples your are presented with. I can't think of a project I've been on where serious bugs for system failures were not caused by some other serious problem upstream of dev. When you're working with competent devs, you'll find most problems are introduced due to poor requirements, miscommunications and unrealistic expectations filtering down from management, and lack of resources applied to test infrastructure and testing. Management should be held accountable for all these things, but instead they scapegoat testers and developers to CYA.