4. 20/05/2014
Keys to
success
Inspect and
adapt
Be creative!
Take
advantage of
your team´s
skillset
Additional
to other
Testing
Quickly find
defects
Add value to
your
customer
TEST
EARLY,
TEST
OFTEN !!!
6. 20/05/2014
Myth 1: Same as Ad-hoc testing
Must be planned and documented
You must know
What has
been tested
When was
it tested
What
defects
where
logged
Some ideas
Testing
tours from
James
Whittaker
Session-
based from
James Bach
Your own
method
Ad-hoc testing is a commonly used term for software testing performed without planning and documentation
7. 5/20/2014
Myth 2: Can´t be measured
Multiple measurement techniques
• Session-Based Test Management SBTM
• Amount of logged defects
• Defects vs. user story complexity
You must be creative
Warning… Warning!
• Don´t be fooled by metrics
8. 20/05/2014
Myth 3: Endless
Difficult to focus on long tasks (> 25 min)
Endless == useless
Must focus on specifics
•Requirements
•Problems
•Complex parts
Stay focused for burst periods (25 min)
10. Myth 4: Can´t reproduce defects
How do you reproduce a defect?
Be a
Explorer
Like David
Livingstone
Toolset
Record video /
audio
Screen capture
Analog
recording (i.e.
Pen and paper)
Empower
developers
…adopt a
developer
12. Myth 5: Only for Agile teams
Inspect and adapt
Insanity: doing the
same thing over and
over again and
expecting different
results.
Look for new ways of
testing
Empower your team by
allowing creativity…
... Do you trust your
team?
… or not? …
13. Myth 6: Not documented
Tester “Lonely Planet”
• User manual
• Online help (the F1 tour)
• Help from third parties
Alternative Tester
• Goes outside the tour (cancelling processes halfway, using
“undo”, doing things twice…)
• Uses uncommonly used functionality or processes
• Always with an objective in mind
Second visit
• You need pictures / notes (screenshots, videos, defects…)
15. As soon as
possible
Defects can
appear in any
phase
... Pretotyping
http://www.pretotyping.org/the-
pretotyping-manifesto-1
20/05/2014
When to start
16. What to expect
• … one more time
Defects
• Key areas
• Increased knowledgeTest plan
17. Tools
Very Important Rol
Should help you to
•Manage testing effort
•Manage test executions
•Manage defects
•Metrics to measure progress
