Context-Driven Testing

 

We base our professional background and our services on Context-Driven Testing

 

"We’re..." (as Michael Bolton, DeveloSense (CA) nicely put’s it) "...aligned with the Context-Driven School of Software Testing, a community of people who believe that testing should respond first and foremost to the needs of the organisation and the project, rather than to “best practices” that may not be best at all in the given context..."

 

 

The Seven Principles of the Context-Driven School of Software Testing

  • The value of any practice depends on its context!
  • There are good practices in context, but there are no best practices!
  • The product is a solution. If the problem isn’t solved, the product doesn’t work!
  • People, working together, are the most important part of any project’s context!
  • Projects unfold over time in ways that are often not predictable!
  • Good software testing is a challenging intellectual process!
  • Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.

 

 

Context-driven testers choose their testing objectives, techniques, and deliverables (including test documentation) by looking first to the details of the specific situation, including the desires of the stakeholders who commissioned the testing.

 

The essence of context-driven testing is project-appropriate application of skill and judgment. The Context-Driven School of testing places this approach to testing within a humanistic social and ethical framework.

 

Ultimately, context-driven testing is about doing the best we can with what we get. Rather than trying to apply “best practices,” we accept that very different practices (even different definitions of common testing terms) will work best under different circumstances.

 

 

© Copyright 2018. All Rights Reserved.