How to mix different testing types to optimize your testing results. Test type classifications and examples of "mix and match" practices. Full webinar recording can be viewed here: https://www.practitest.com/qa-learningcenter/webinars/mixing-testing-types-to-improve-your-work/

1. Joel Montvelisky
Chief Solution Architect
Simplify Test Management
Mixing Test Types to
Optimize Your Results

2. What do we want to cover today?
• Why do we need different types of Tests?
• Some “common” testing type classifications
• Testing types review
• Mixing testing types as part of your MTP
• Questions and Answers

3. About
 SaaS ALM Solution
 Simple & Intuitive – yet – Methodological & Flexible
 Integrates with Jira, Selenium, Jenkins, Pivotal Tracker, QTP,
Bugzilla, Ranorex, SoapUI, etc…
 Best Darn Support in the Business 

4. Show of hands!
“Raise your hand”
if you consciously
use different types
of testing as part
of your work

5. Why Do We Need
Different
Types of Tests?

6. Why Do We Need Different Types of Tests???
Let’s do a short exercise…
Close your eyes and imagine the following professionals:
 A Doctor
 A Wood Craftsman
 A Soldier
Knowledge
Experience
Tools

7. And So… Why Do We Need
Different Types of Tests?

8. Some “Common”
Test Type
Classifications

9. Some Test Type Classifications
 Based on the phase of the project
 Based on the understanding of the code
 Based on the rigidity of the test
 Based on the tools used
 Based on the attribute tested
And more…

10. Test Type Classifications -
Based on “Project Phase”
Unit
Integration
System
Acceptance
Originated with V model
It is also very valuable
in Agile and all approaches
Main Value: Focuses on specific aspects of the product in an
incremental way, each time spot-lighting a different
type of interaction

11. Test Type Classifications -
Based on “Understanding of the Code”
Black White
Grey
Black Box is done without knowing
the code at all
White Box is done with full
understanding of the code
>> Most testing is actually Grey
Box…
Main Value:
There is value in understanding the weakness of the code
while testing.
But, there is also a the known drawback of “sticking to the
known paths”, this is broken by Black Box Testing.

12. Test Type Classifications -
Based on “Rigidity of the Test”
Scripted Context Driven
Scripted tests are based on written testing scripts and steps.
Context Driven testing is based on learning, planning and
running the tests simultaneously in the same operation.
Main Value:
Most testing is done somewhere in between. Depending
on the experience of the tester and nature of the test,
sometimes it is better to go in one direction or the other.

13. Examples of
Context Driven Tests
- Exploratory Testing –
Learn, plan, test & document simultaneously
- Session Based Testing –
Test charters are created for each ET session
- Bug Hunts –
Pair testing or team testing, focused on finding bugs
- “Soap Opera” Scenarios -
Exaggerated role playing exercises

14. Test Type Classifications -
Based on the “Tools Used”
Main Value: There are tons of value in automating repetitive
tasks, but not all tests can or should be automated.
Automation includes:
Functional Automation - Load/Stress - API testing -
Data Creation - Environment Setup - etc.
Manual Testing Automated Testing
Vs.

15. Test Type Classifications -
Based on the “Attribute Tested”
Functional
Tests
Non-Functional
Tests
Functional tests checks the “regular” user interactions with
the system
Non-Functional tests concentrate on the other attributes
that the software needs to comply with
Main Value:
There is a wide variety of attributes that need to be
tested that are not related to the “regular” functionality
of the software.

16. Examples of
Non-Functional Tests
- Usability Testing
- Maintainability Testing
- Compatibility Testing
- Compliance Testing
- Security Testing
- Recovery Testing
- Install/Uninstall Testing
- Upgrade Testing
- Accessibility Testing
- Portability Testing
- I18N Testing
- Volume Testing

17. OK …
So Now What?!

18. Back to our wall with the tools…

19. Mixing Different Test Types
as Part of the Master Test Plan*
My MTP’s ToC
(only an example!)
1. Objectives
2. Testing scope
3. Testing matrix
4. Risks
5. Software / Hardware
requirements
6. Preparations
6. Task schedules
6. Calendar & Resources
6. External references
6. Contact information
(*Reminder from the previous webinar)

20. Questions & Answers
Mixing Testing Types

21. About
 SaaS ALM Solution
 Simple & Intuitive – yet – Methodological & Flexible
 Integrates with Jira, Selenium, Jenkins, Redmine, Bugzilla, QTP,
Ranorex, SoapUI, etc…
 Best Darn Support in the Business 

22. Thank You!
joel@practitest.com
http://qablog.practitest.com