These are the underlying principles that form the foundation of how I approach software testing

  • Testing is learning about the product to gather information that can enable informed decisions to be made
  • The situation drives the approach to testing. Every situation is unique, so every approach to testing should be unique.
  • Testers are not the gatekeeper of quality, but they may provide recommendations if they have the experience to do so
  • Tools & automation help testing, they do not replace it
  • Testing doesn’t start with a supposedly finished product
  • Questioning of the requirements is aimed at a human, not a document
  • Quality of the software is the responsibility of the whole development team
  • Close collaboration & frequent feedback are key to the delivery of successful software
  • Business stakeholders need to take an active interest in their software projects to help them succeed
  • If the code isn’t in Production, it’s not making money

These principles are the result of over 15 years of testing and are underpinned by the following:


Back to About