Story of a context driven tester

1. Context Driven Tester
Wasiqul Huq

2. THE TRADITIONAL WAY OF TESTING
• The right way
• The best practice
• The practical approach

3. BIRTH OF CONTEXT DRIVEN TESTING

4. 7Basic Principles
1. The value of any practice depends on its context.
2. There are good practices in context, but there are no best
practices.
3. People, working together, are the most important part of
any project’s context.
4. Projects unfold over time in ways that are often not
predictable.
5. The product is a solution. If the problem isn’t solved, the
product doesn’t work.
6. Good software testing is a challenging intellectual process.
7. 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.

5. PRINCIPLES IN ACTION
• Invalid metrics are dangerous
• The value of a test case is in its ability to be
informative for reducing uncertainty.
• A passed test does not mean that it may not
fail in ways that you and your script is
ignoring.
• Automated testing is not manual testing done
automatically.

6. WHY CONTEXT DRIVEN TESTING?
• Do you value more in individuals rather than
their interactions over processes or tools?
• Do you value more in seeing working software
over documentation?
• Do you value more in responding to change
over following the plan?

7. Our Believe
• “So, you don’t believe in documentation?”
Not true; we do believe in documentation. But
we believe in communication more.
• “Exploratory testing? So that’s manual testing,
you don’t believe in test automation?” Not
true; we do believe in automation as a tool.

8. THANKS 
WASIQUL HUQ