ET. My way
0 likes653 views
The document discusses exploratory testing, highlighting it as a method where tests are designed and executed concurrently while exploring the software. It introduces various heuristics for testing, such as feature, complexity, and user tours, which guide testers in evaluating different aspects of a product. The document also emphasizes the importance of structured execution through specific charters and review sessions.
ET. My way
- 2. WHAT IS EXPLORATORYTESTING? Exploratory Testing is a style of testing in which you explore the software while simultaneously designing and executing tests, using feedback from the last test to inform the next - Elisabeth Hendrickson http://testobsessed.com/2006/04/rigorous-exploratory-testing/ @sharathb http://testtotester.blogspot.co.uk
- 3. LEARNING HEURISTICS TOURING HEURISTIC - by michaeldkelly • Feature tour • Complexity tour • Claims tour • Configuration tour • User tour • Testability tour • Scenario tour • Variability tour • Interoperability tour • Data tour • Structure tour • Feature tour: Move through the application and get familiar with all the controls and features you come across. • Complexity tour: Find the five most complex things about the application. • Claims tour: Find all the information in the product that tells you what the product does. @sharathb http://testtotester.blogspot.co.uk
- 4. LEARNING HEURISTICS TOURING HEURISTIC - by michaeldkelly • Feature tour • Complexity tour • Claims tour • Configuration tour • User tour • Testability tour • Scenario tour • Variability tour • Interoperability tour • Data tour • Structure tour • Configuration tour:Attempt to find all the ways you can change settings in the product in a way that the application retains those settings. • User tour: Imagine five users for the product and the information they would want from the product or the major features they would be interested in. • Testability tour: Find all the features you can use as testability features and/or identify tools you have available that you can use to help in your testing. • Scenario tour: Imagine five realistic scenarios for how the users identified in the user tour would use this product. @sharathb http://testtotester.blogspot.co.uk
- 5. LEARNING HEURISTICS TOURING HEURISTIC - by michaeldkelly • Feature tour • Complexity tour • Claims tour • Configuration tour • User tour • Testability tour • Scenario tour • Variability tour • Interoperability tour • Data tour • Structure tour • Variability tour: Look for things you can change in the application - and then you try to change them. • Interoperability tour:What does this application interact with? • Data tour: Identify the major data elements of the application. • Structure tour: Find everything you can about what comprises the physical product (code, interfaces, hardware, files, etc...). @sharathb http://testtotester.blogspot.co.uk
- 6. LEARNING HEURISTICS TOURING HEURISTIC - by michaeldkelly (customised) @sharathb http://testtotester.blogspot.co.uk
- 7. TESTING… in most places is limited to… SUT intended inputs intended outputs @sharathb http://testtotester.blogspot.co.uk
- 8. EXPANDED BLACK BOXTESTING MODEL by Douglas Hoffman @sharathb
- 9. DESIGN HEURISTICS develop your own… @sharathb http://testtotester.blogspot.co.uk
- 10. EXECUTION SBTM • develop specific charters, • time-box an uninterrupted work session, • create a reviewable result, and • review/debrief the session afterwards. @sharathb http://testtotester.blogspot.co.uk
- 11. EXECUTION for analysis, interpretations (develop your own) @sharathb http://testtotester.blogspot.co.uk
- 12. EXECUTION for analysis, interpretations (develop your own) @sharathb http://testtotester.blogspot.co.uk
- 13. EXECUTION for analysis, interpretations (develop your own) @sharathb