Embed Size (px)
DESCRIPTION
Many of the customers I am speaking with are dealing with two mayor developments. First, there is a very strong urge to reduce costs in general and cost and speed of testing in particular. The other trend is of course being agile. Combining the two trends I conclude that we testers need to improve the efficiency and quality of our work. I believe enriching our toolkit with better techniques, tools and methods will help us to do so. Since the traditional test design techniques are quite powerful, our quest for new techniques should focus on those that helps us to be more efficient in an agile context. During the session I will give examples of techniques, tools and methods that are already available in other disciplines and explain how they can be useful for us. One of the sources I'll use is the agile extension of the BABOK guide, The Business Architects Body of knowledge contains a rich source of valuable techniques. I'll distinguish between techniques that we need to actually design and perform our tests, create error situations and detect errors. And on the other hand supporting techniques that help us to determine scope, improve our process and moderate efficient sessions with our team. Examples I'll give include: How to provoke and recognize errors, Story decomposition, Story mapping, Value stream mapping, using persona's, Business Capacity Model, Subway mapping, Process simulation and Gaming. The presentation will suggest techniques, tools and methods that can be used by the participants straight away. The presentation will make you aware that valuable techniques are already available in various sources. I'll introduce a classification model helps them to seek and recognize additional techniques. These techniques enable testers to show their other face: participating in and moderating sessions and coach team members with using the right tools/methods.
Citation preview
Efficiency with the right techniques, tools & methods
Derk-Jan de GroodBelgium Testing Days 2014
1
Enrich your Toolbox
My 1st Pocket knife
2
3
4
5
Definition tool
A tool is any aid
that helps you to
do a better job
faster.
Checklist
These include:
Templates Checklists Heuristics Physical tool
Application Techniques Processes Frameworks
Models Work forms etc
6
Tools: like word processor, excel, outlookModels: e.g. six hats from bono, but also an excel model to verify your outcome.Facilitation methods: like brown paper session, risk sessions, etc..Techniques: like design techniques, communication techniques, Frameworks: e.g. COBIT, SCRUM, etc
7
8
The wrong tool…
9
Searching for tools
10
11
What do we do when testing?
12
Analyse
13
15
Challenge
16
James Wittacker
17
Some examples
Reduce the bandwidth of the network connection
Make the network fail
Limit the disk space available for the application
Interruptions
SQL statement injection
Searching for overflows (256, 1024, 32767, etc…)
Change the order of activities
18
Think, Challenge and Observe
20
Obs
erve
Test Recognition Techniques
21
Inconsistencies: internal
Inconsistencies: external
Absences
Extras
Agony
Delays
Searching for tools
Two Trends
23
24
Agile testing Characteristics
25
• Cooperation and teamwork• Variety in cooperation and workshops• Roles merging and testers get involved
into design and development• Automated or Exploratory testing• Keep track on progress and quality
Searching for tools
27
The IIBA- BABOK guide…
Jan Jaap Cannegieter (QATest 30-10-2013)
Scoping techniques
29
PRIMA
30
KANO
31
1. Persona’s
2. Qualifiers
3. Disqualifiers
Story Decomposition
32
MINIMAL
MARKETABLE
FEATURE
Story Mapping
33
Getting a grip on the project
34
Kanban
35
36
Release Charts
Subway mapping
37
Business Benefit (MFF)
38
Lets do it a little different, this time
Facilitation Methods
39
Facilitation methods
Standup meetings
Mind map
Brown paper session
Sorting and Prioritizing
Process simulation
Gaming
Role playing
Demo
Interview techniques
40
Improvement techniques
41
Value Stream Map
42
Service Virtualisation
43
Assume a Process within a system that requires interaction with other systems.
43
Step 1 Step 2 Step 3 Step 4
Ext Syste
m
Ext Syste
m
Ext Syste
m
Considerations that define the waste on the interface:• How often used • Error proneness of
the interface• Delay in processing• Manual effort on the
interface• Cost for processing• Ability to test rainy
scenarios’• Easy of investigating
errors• Support issues• High risk due to not
testing at all or error situations
1 = delay
(waste) per day
based on normal
usage (or testing)
1 3
5
Business Capacity model
44
Persona’s45
Persona’s46
Draw-back
When showing one techniques, people are are likely to state that they missed another technique.
48
Test Design
Error Creation
Error Detecting
Focus (Scope & Prio)
GR
IP(P
lanning &
Co
ntrol)
Test Improvement
Fac
ilita
tion
Met
hods
Root Cause Analysis
techniques*
*Thanks to Jan van Moll
Test Design
Error Creation
Error Detecting
Focus (Scope & Prio)
GR
IP(P
lanning &
Co
ntrol)
Test Improvement
Fac
ilita
tion
Met
hods
Root Cause Analysis
techniques*
*Thanks to Jan van Moll
Cause Effect graphing
ECFA (Events and Causal Factors
Analysis)
Current Reality Tree
Change Analysis
Why-Because Analysis
Re-enactment
Fault Tree Analysis
MORT
Common Cause Analysis
Barrier Analysis
MES (Multi-Linear Event
Sequencing)
STEP (Sequential Timed Event
Plotting)
CIT (Critical Incident Technique)
Is-Is Not Matrix
5-times Why
HFA (Human Factors
Assessment)
Storytelling
Reality charting
Wrap-up
51
Quick replay
52
53
54
More reading…
55
SUCCESS !
Derk-Jan
ValoriColtbaan 4a3439 NG NIEUWEGEINThe Netherlands
[email protected]+31(0)651807878@DerkJanDeGroodhttp://djdegrood.wordpress.com
Derk-Jan
56
Slides: http://www.slideshare.net/DerkJandeGrood/unpack-your-toolkit-becoming-more-effective-with-the-right-tools-and-techniques
