The document discusses the importance of testing and provides a simple framework for developing a testing approach. It advocates considering three key aspects of testing: test execution, planning, and approach. The framework involves identifying the user interaction, technical stack, and potential changes involved in the system or feature being tested. This information is then used to determine the appropriate scope and levels of testing, from unit to system to acceptance. Applying the framework helps define responsibilities, needs, and assess the impact of any changes. The document provides examples of using the framework for both complex and simple systems. It concludes by emphasizing the value of information provided by testing and using the visual modeling technique for planning testing activities.

1. We need to talk about… Testing
Paul Theyers
Principal Consultant – Assurity

2. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• To understand the value of testing
• Share a simple framework of how to approach testing
(3 min acid test)
Objectives

3. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Think about what testing means to you?
Your Understanding
http://blog.gfader.com/2010/10/why-are-automated-tests-so-important.html

4. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• So tell me… what did you think of when thinking about
testing?
1. Test Execution
2. Test Planning
3. Test Approach to the above 2?
Your Thoughts

5. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Provides information to make decisions
Testing Value Statement
http://lifehacker.com/how-to-factor-your-personality-into-your-decision-makin-1674643269

6. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• We tend to talk about “test execution”
• We NEED to talk about all 3 (execution, planning and
approach)
Just do it

7. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Why is it important?
• The outcome is a test Strategy
Test Approach
/http://www.avionale.com/2011/01/singapore-airlines-airbus-a380-2.html/

8. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Test Strategy talks about “what we will do”
• Test Plan talks about “how we will do it”
Strategy vs Plan
https://corentium.com/radonview/

9. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
So… what’s important to testing
https://www.flickr.com/photos/softwaretestingclu
b/7534365896/sizes/h/in/photostream/

10. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Simple framework
Scary…
https://corentium.com/radonview/

11. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• User interaction
• Technical stack
• Change, being added, removed?
Just 3 simple inputs…

12. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Technical Stack… Spat!
System A System B System D System F
System C
System E

13. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
User Interaction
System A System B System D System F
System C
System E
§
§

14. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Change…
System A System B System D System F
System C
System E
Change
§
§

15. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Test Scope
System A System B System D System F
System C
System E
Change
§§
§
§
§
§ Unit Test, Unit
Integration and
System Test
§§
§
§ System Integration Test
§ Acceptance Test
§

16. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Scope of test level required
• Assign responsibility
• Define environment needs
• Data requirements
• Simple to assess impact of any change
• Apply development methodology – Traditional/Agile
So why does that help…

17. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Traditional – V model
• Agile – Test Quadrant
• Automation Pyramid
Development Methodology

18. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Big solution
• Simple service
• BAU change
Examples

19. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Complex Solution
https://corentium.com/radonview/

20. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
WebClient–PCBrowser/B2BClient
Business Process Management Component
Business Integration
Component
Web User Interaction
Component
Service Based
Component
Business Object
Component
WebClient–PCBrowser/B2BClient
Business Process Management Component
Business Integration
Component
Web User Interaction
Component
Service Based
Component
Business Object
Component
Change
WebClient–PCBrowser/B2BClient
Business Process Management Component
Business Integration
Component
Web User Interaction
Component
Service Based
Component
Business Object
Component
Change

21. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Mobile
Client
Bank Systems
Mobile
Cleint
Other Bank System
Payment gateway
Mobile
Client
Bank Systems
Mobile
Cleint
Other Bank System
Payment gateway
Simple Mobile Payment System
https://corentium.com/radonview/
Mobile
Client
Bank Systems
Mobile
Client
Other Bank System
Payment gateway
Mobile
Client
Bank Systems
Mobile
Client
Other Bank System
Payment gateway
Mobile
Client
Bank Systems
Mobile
Client
Other Bank System
Payment gateway
Change
Mobile
Client
Bank Systems
Mobile
Client
Other Bank System
Payment gateway
Change

22. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Change… 1
Change
Change

23. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Change 2
Change
Change

24. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Questions…

25. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
• Start by using a visual model early
• Remember it’s the information testing provides
• Use this technique to static test
Conclusion

26. Assurity Consulting Limited • Commercial in Confidence • Copyright 2016
Thanks for listening

27. Thanks for listening
Any Questions?