Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Real Testing Scenario Strategy - The Role of Exploratory Testing

397 views

Published on

• Where to use exploratory testing
• Tools you can use (capture tools like bugreplay), tracking tools like SpiraTest’s new exploratory mode, etc.
• How to fit it into your sprint plan and best practices to working with developers to identify and fix issues found in exploratory testing.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Real Testing Scenario Strategy - The Role of Exploratory Testing

  1. 1. Real Testing Scenario Strategy: The Role of Exploratory Testing Presented by Adam Sandman Inflectra Corporation QA Geek Week | Hertzliya, Israel, 2018
  2. 2. 2 | 6/30/2018 QA Geek Week Conference | June 2018 About Me  Adam Sandman was a programmer from the age of 10 and has been working in the IT industry for the past 20 years.  Currently Adam is a Director of Technology at Inflectra Corporation, where he is interested in technology, business and innovation.  Adam lives in Washington, DC, USA
  3. 3. 3 | 6/30/2018 QA Geek Week Conference | June 2018 Takeaways 1. Why and where to use exploratory testing 2. Tools you can use for exploratory testing 3. How to fit exploratory testing into your sprints
  4. 4. Why Use Exploratory Testing?
  5. 5. Testing = Manage Technical Risk
  6. 6. All The Automated Tests Pass Should We Ship?
  7. 7. 7 | 6/30/2018 QA Geek Week Conference | June 2018 User Stories Requirements Automated Testing Exploratory Testing: Navigating Edges
  8. 8. 8 | 6/30/2018 QA Geek Week Conference | June 2018 Exploratory Testing: Navigating Edges The Actual System
  9. 9. 9 | 6/30/2018 QA Geek Week Conference | June 2018 Exploratory Testing: Navigating Edges The Actual System Edge Cases
  10. 10. 10 | 6/30/2018 QA Geek Week Conference | June 2018 Exploratory Testing: Where & Why Good testers find issues that no one knows about Exploratory testing finds those edge cases It’s the unknown ‘unknowns’ that trip you up It’s particularly useful when the functionality is still being formed in early sprints
  11. 11. Tools That Can Help
  12. 12. 12 | 6/30/2018 QA Geek Week Conference | June 2018 Real-Time Capture Tools Tools like BugReplay let you easily capture video, screenshots, logs, network traffic, etc.
  13. 13. 13 | 6/30/2018 QA Geek Week Conference | June 2018 Exploratory Test Management Tools Tools that let you document your testing, capture “Tasks” that are not defects
  14. 14. How to Incorporate into Sprints
  15. 15. 15 | 6/30/2018 QA Geek Week Conference | June 2018 Session-Based Testing  Applies some basic structure to exploratory testing  Time-boxed session where you focus on a specific objective or set of user stories  Test Cases are basically just a description of the objective or area being tested  You can link it to the requirements and user stories  Measuring functionality coverage is a good thing!  Executing a test case means following an unstructured path that tests the objective, recording all observations, not just problems.  Even if functionality is not finished, the observations are useful to the developer
  16. 16. 16 | 6/30/2018 QA Geek Week Conference | June 2018 Challenges of Exploratory Testing  Sometimes it’s hard to know if it’s broken or ‘just not done yet’  Observations may not be actual issues  The Units Tests all Pass, Why is it Broken?  We can both read the test run report and get completely different information!  Test Runs end up being a lot of unrelated issues that can be hard to trace – Solution use Tasks!  When to transition from recording test runs and tasks to logging defects?
  17. 17. Questions?
  18. 18. Thank you for attending. See you next year :-)

×