When to Compromise on Testing


Several times over the last few years of working as a tester, I have found myself making compromises on the way that I have been testing, and generally felt very uncomfortable about doing so. Everyone will tell you that compromise in testing is inevitable, but that never makes it any easier. It is never possible to get the perfect mix of resources, skilled testers, equipment to test upon, enough time to plan and prepare for testing, or even to run all of the test scripts, let alone re-test all of the software fixes.

Managers are forever telling you that when they used to write and test software they did it this way, or that way, someone else will suggest that you aren’t using the right toolset, and even your own testing team may disagree with the general direction or method. Notwithstanding all of that, and the fact that developers don’t make mistakes do they, the users will then blame you personally for every bug that they find!

This talk does not offer a silver bullet solution, but will take you through the testing lifecycle, identifying the areas where compromise is most commonly called for, and show you the techniques that I have found successful in managing and controlling that compromise without losing integrity. And also a few of the pitfalls!



Presented at:

1. BCS SIGiST, London – Sep 2000
2. EuroSTAR, Copenhagen – Dec 2000