This document provides an introduction to context driven testing. It discusses establishing the proper mindset of testing for business value by understanding who uses the software, how it is used, and why it exists. Key aspects of context driven testing are exploring where bugs that matter can be found through experimentation and learning, using system and domain knowledge to facilitate analysis that considers the business needs, project risks, product risks, and available resources defined by the context. The document emphasizes the importance of curiosity and complementary principles of agility and context driven development like responding to change, valuing individuals and interactions, and ensuring the product solves the problem.

1. READY, SET, GO!
Introduction to Context Driven
Testing
Anna Royzman
@QA_nna

2. MINDSET

3. TESTING FOR
BUSINESS VALUE

4. - BY WHO
- HOW
- WHY
SOFTWARE IS USED

5. WHERE TO FIND
BUGS THAT
MATTER

6. EXPERIMENT

7. LEARNING

8. SKILLSET

9. TEST
METHODOLOGIES

10. SYSTEM QUALITY
ATTRIBUTES
“-ilities”, or non-functional
requirements

11. SYSTEM/DOMAIN
KNOWLEDGE

12. COMMUNICATION

13. FACILITATION

14. ANALYSIS

15. CONTEXT:
- BUSINESS NEEDS
- PROJECT RISKS
- PRODUCT RISKS
- RESOURCES

16. CURIOSITY

17. COMPLEMENTARY PRINCIPLES
Agile Manifesto
• Responding to
change over following a
plan
• Individuals and
interactions over
processes and tools
• Working software over
comprehensive
documentation
Context Driven School
• Projects unfold over
time in ways that are
often not predictable.
• People, working
together, are the most
important part of any
project’s context.
• The product is a
solution. If the problem
isn’t solved, the
product doesn’t work.

18. CONTEXT-DRIVEN