Exploratory testing myths Romanian Testing Conference 2014

982 views
896 views

Published on

Let's uncover some myths and misconceptios of Exploratory Testing

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
982
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Exploratory testing myths Romanian Testing Conference 2014

  1. 1. Exploratory Testing myths
  2. 2. luis.fraile@vsanywhere.com CTO / Co-founder @lfraile - @vs_anywhere www.lfraile.net http://geeks.ms/blogs/lfraile/ Luis Fraile
  3. 3. 16/05/2014 Exploratory testing?
  4. 4. 16/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 !!!
  5. 5. Some myths… 16/05/2014
  6. 6. 16/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 Context- based testing 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. 7. 5/16/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. 8. 16/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)
  9. 9. 16/05/2014
  10. 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 
  11. 11. 16/05/2014 Adopt a developer
  12. 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. 13. Myth 6: Not documented What we think of documentation? But there are: •Video •Screenshots •Audio •Bugs •New test plans …
  14. 14. Did we change your mind?
  15. 15. As soon as possible Defects can appear in any phase ... Pretotyping http://www.pretotyping.org/the- pretotyping-manifesto-1 16/05/2014 When to start
  16. 16. What to expect • … one more time Defects • Key areas • Increased knowledgeTest plan
  17. 17. Tools Very Important Rol Should help you to •Manage testing effort •Manage test executions •Manage defects •Metrics to measure progress
  18. 18. Experience and experiment MOST IMPORTANT THING !!!!!
  19. 19. References ● Agile Testing from Lisa Crispin y Janet Gregory ● Anutthara Baradwaj (Microsoft) http://blogs.msdn.com/b/anutthara ● James Bach http://www.satisfice.com/blog/ ● James Whittaker (Google Microsoft) http://blogs.msdn.com/b/jw_on_tech/ ● Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design ● http://thecodinglove.com/
  20. 20. Thanks for your time Luis Fraile // luis.fraile@vsanywhere.com // @lfraile // @vs_anywhere 16/05/2014

×