The document outlines 7 thinking tools to help with rapid testing: 1. Landscaper - Do a survey to understand the big picture 2. Persona map - Map out who uses what 3. Scope map - Map out user expectations 4. Interaction map - Map what may affect what 5. Environment map - Map test environments 6. Scenario creator - Create test scenarios 7. Dashboard - Stop, analyze, and refine These tools are part of an immersive session testing approach using reconnaissance, exploration, and rest/recovery phases to facilitate rapid yet thorough scientific exploration. A related SaaS tool called doSmartQA will offer these tools and interested users can email the founder for

1. Ashok Thiruvengadam
Founder & CEO
www.STAGSoftware.com
www.linkedin.com/in/ashokstag
7 Thinking Tools
to Test Rapidly
SmartQA Series Webinar

2. 2
Manual testing | Automated testing
Two phrases that some people use to describe our practice
Jeez, they have a terrible way with words!

3. 3
It is time we used Intellectual | Tool-supported

4. 3
It is time we used Intellectual | Tool-supported
Think well. Exploit tools to do.

5. 4
In current times, speed is everything, right?

6. 4
In current times, speed is everything, right?
What can we do test quickly ?
Use tools.Automate. Right?

7. 4
In current times, speed is everything, right?
Wait a minute!
This is about execution, right?
What about prior activities?
What can we do test quickly ?
Use tools.Automate. Right?

8. 5
to answer, let us ask the basic question
what is testing after all?

9. 6
testing is exploration

10. 7
testing is scientific exploration

11. 7
testing is scientific exploration
and exploration is a human activity
aided by tools & technology

12. 8
how can we do
scientific exploration rapidly?

13. 8
how can we do
scientific exploration rapidly?
by using tools that help us
think better and do faster

14. 9
we all know about
a variety of test tools that help us automate
system setup, execution, static analysis, report, manage…
at different phases of lifecycle to “do faster”

15. 9
we all know about
a variety of test tools that help us automate
system setup, execution, static analysis, report, manage…
at different phases of lifecycle to “do faster”
let’s examine tools that help us
“think better”

16. 10
what is the first thing you do
before you embark on an exploration?
do a survey “reconnaissance"

17. 11
Tool #1: Landscaper
do survey, understand the big picture

18. 11
Tool #1: Landscaper
do survey, understand the big picture
persona
who are the
end users
e.g ELearning system
Persona
Administrator
Student
Supervisor

19. 11
Tool #1: Landscaper
do survey, understand the big picture
persona
who are the
end users
entities
what do you
want to test
component, features
requirements, flows
e.g ELearning system
Persona
Administrator
Student
Supervisor
Feature
Create User
Upload content
Requirement
Go through lessons in courses
Take final assessment
Flow
Complete course, by taking it and
doing the final assessment

20. 11
Tool #1: Landscaper
do survey, understand the big picture
persona
who are the
end users
entities
what do you
want to test
component, features
requirements, flows
attributes
what do you
want to test for
e.g ELearning system
Persona
Administrator
Student
Supervisor
Feature
Create User
Upload content
Requirement
Go through lessons in courses
Take final assessment
Flow
Complete course, by taking it and
doing the final assessment
Migration
All course info of 2.5, 2.7, 3.0
to be ‘migrate-able’
Performance
Video streaming should
commence in a max of 2s with
500 concurrent users.

21. 11
Tool #1: Landscaper
do survey, understand the big picture
persona
who are the
end users
entities
what do you
want to test
component, features
requirements, flows
attributes
what do you
want to test for
environment
where do you
want to test on?
e.g ELearning system
Persona
Administrator
Student
Supervisor
Environment
OS Mac,Windows, Linux
Browser Firefox, Chrome, IE11
Database Mongo,MySQL,PostgreSQL
MobileOS Android,IOS
Device Laptop,Tablet,Mobile
Feature
Create User
Upload content
Requirement
Go through lessons in courses
Take final assessment
Flow
Complete course, by taking it and
doing the final assessment
Migration
All course info of 2.5, 2.7, 3.0
to be ‘migrate-able’
Performance
Video streaming should
commence in a max of 2s with
500 concurrent users.

22. 12
now that you have done the survey,
what next?

23. 12
now that you have done the survey,
what next?
create maps
to guide you and chalk out routes

24. 13
Tool #2: Persona map
map out who uses what
who uses what
persona
who are the
end users
entities
what do you
want to test
component, features
requirements, flows

25. 13
Tool #2: Persona map
map out who uses what
who uses what
persona
who are the
end users
entities
what do you
want to test
component, features
requirements, flows

26. 14
Tool #3: Scope map
map out user’s expectations
attributes
what do you
want to test for
what-to-test-for-what
entities
what do to you
want to test
component, features
requirements.flows

27. 14
Tool #3: Scope map
map out user’s expectations
attributes
what do you
want to test for
what-to-test-for-what
entities
what do to you
want to test
component, features
requirements.flows
Migration
Security
Performance
Load

28. 15
Tool #4: Interaction map
map out what may affect what, to intelligently regress
entities
what do you
want to test
component, features
requirements, flows
F1 —> F2
F1 —> Flow3

29. 15
Tool #4: Interaction map
map out what may affect what, to intelligently regress
entities
what do you
want to test
component, features
requirements, flows
F1 —> F2
F1 —> Flow3

30. 16
Tool #5: Environment map
map out environments to test on
environment
where do you
want to test on?
Env #1
Env #2
…

31. 16
Tool #5: Environment map
map out environments to test on
environment
where do you
want to test on?
Env #1
Env #2
…

32. 17
now that we have the maps, what do we do next?

33. 17
chalk out the routes
i.e. “test design” - come up with scenarios.
now that we have the maps, what do we do next?
Now you are ready to explore.

34. 18
Tool #6: Scenario creator
create test scenarios
L4: Behaviour correctness
L1: Input correctness
L3: Structural integrity
L2: Interface correctness
L5: Flow correctness
L6: Environment correctness
L7: Attribute correctness
L8: Deployment correctness
L9: End user value
18
component test scenarios
feature test scenarios
requirement test scenarios
flow test scenarios
use techniques
use experience
be creative
learn and revise
use smart checklists
level-wise
Robust Test Design powered by HBT
(Hypothesis Based Testing)

35. 18
Tool #6: Scenario creator
create test scenarios
L4: Behaviour correctness
L1: Input correctness
L3: Structural integrity
L2: Interface correctness
L5: Flow correctness
L6: Environment correctness
L7: Attribute correctness
L8: Deployment correctness
L9: End user value
18
component test scenarios
feature test scenarios
requirement test scenarios
flow test scenarios
use techniques
use experience
be creative
learn and revise
use smart checklists
level-wise
Robust Test Design powered by HBT
(Hypothesis Based Testing)
Table 1
(L4) Func. Behavior
Close a unresolved question
Re-open a closed question
Reply to an open unresolved
question
Edit reply for a question
Table 1-1
(L1) Input validation
Null inputs
Beyond boundaries
Duplicate values

36. 19
now you are ready to explore

37. 20
understand that
a map is not the terrain
as you explore, observe, learn, adapt, improvise, refine

38. 21
observe, learn, adapt, improvise, refine

39. 21
observe, learn, adapt, improvise, refine
persona entities
attributes environment
…the landscape
persona map scope map
interaction map environment map
…the maps
L4: Behaviour correctness
L1: Input correctness
L3: Structural integrity
L2: Interface correctness
L5: Flow correctness
L6: Environment correctness
L7: Attribute correctness
L8: Deployment correctness
L9: End user value
…the routes

40. 22
ok, what next?
rest and recover
i.e. stop, analyse and refine

41. 23
Tool #7: Dashboard
stop, analyse and refine
23
adequacy
scenarios
good enough
progress
are we
on track?
quality
how good is
the system?

42. 23
Tool #7: Dashboard
stop, analyse and refine
23
adequacy
scenarios
good enough
progress
are we
on track?
quality
how good is
the system?
Inputs
1. Attributes considered?
2. Environ. considered?
3. Scenarios at all levels?
4. +/- distribution ok?
5. All personas covered?
Use Maps+Routes

43. 23
Tool #7: Dashboard
stop, analyse and refine
23
adequacy
scenarios
good enough
progress
are we
on track?
quality
how good is
the system?
Inputs
1. Attributes considered?
2. Environ. considered?
3. Scenarios at all levels?
4. +/- distribution ok?
5. All personas covered?
Use Maps+Routes
1. wrt attributes
2. wrt attributes
3. wrt entities
4. wrt interactions
5. wrt persona
Use Maps+Routes+Exec Info
Activities (plan vs.actual)

44. 23
Tool #7: Dashboard
stop, analyse and refine
23
adequacy
scenarios
good enough
progress
are we
on track?
quality
how good is
the system?
Inputs
1. Attributes considered?
2. Environ. considered?
3. Scenarios at all levels?
4. +/- distribution ok?
5. All personas covered?
Use Maps+Routes
1. wrt attributes
2. wrt attributes
3. wrt entities
4. wrt interactions
5. wrt persona
Use Maps+Routes+Exec Info
Activities (plan vs.actual)
1. wrt attributes
2. wrt attributes
3. wrt entities
4. wrt interactions
5. wrt persona
Use Maps+Routes+Exec Info
Outcomes

45. 24
let’s summarise
our scientific exploration
using the ”7 Tools to Think Better”

46. 25

47. 25
Tool #1: Landscaper
do survey, understand the big picture
Tool #5: Environment map
map out environments to test on
Tool #2: Persona map
map out who uses what
Tool #4: Interaction map
map out what may affect what
Tool #3: Scope map
map out user’s expectations
Reconnaissance
do survey, make maps
Tool #6: Scenario creator
create test scenarios
Exploration
observe, search, learn, refine
Tool #7: Dashboard
stop, analyse and refine
Rest and recover
stop, analyse and refine

48. 26
so how can one apply this?

49. IMMERSIVE SESSION TESTING “IST”
Reconnaissance
Exploration
Rest & Recover
S1 S2
S3
S4
S5
done in sessions of 60-90 minsconsists of THREE phases
from STAG Software
by using
a session based approach based on Hypothesis Based Testing

50. 28
the tools outlined here and more will be
available as a SaaS tool doSmartQA shortly
we are keen to trial this with select users
email me if you are interested
‘ash at stagsoftware dot com’

51. testing is scientific exploration
7 Thinking Tools
to Test Rapidly
SmartQA Series Webinar
doSmartQA SaaS tool
email me if you are interested
‘ash at stagsoftware dot com’