1. Step 1
   1. Requirements-Based Testing
      1. Limit the scope to make it manageable
         1. use BDD
            1. Some notes about BDD
            2. https://www.xmind.net/m/9vqi/
      2. Some notes: How we can test without formalized requirements
         1. https://www.xmind.net/m/yAnW/
   2. Use Heuristic and Mnemonics
      1. Heuristics are simply experience-based techniques for problem solving, learning, and discovery
      2. Test Heuristics Cheat Sheet Elisabeth Hendrickson
         1. http://testobsessed.com/wp-content/uploads/2011/04/testheuristicscheatsheetv1.pdf
      3. Heuristic Test Strategy Model James Bach
         1. http://www.satisfice.com/tools/htsm.pdf
      4. Use Mnemonics
         1. RCRCRC
            1. https://www.xmind.net/m/q3gr/
         2. http://www.qualityperspectives.ca/resources/#mnemonics
2. Step 2
   1. Session-based Testing
      1. Structure exploratory testing to allow large-scale implementations
         1. http://www.satisfice.com/articles/sbtm.pdf
         2. http://www.satisfice.com/sbtm/
      2. Define a goal for your session
         1. Explore <target> with <resources> to discover <information>
      3. Timebox session
      4. Charter
3. Step 3
   1. Test Tours
      1. Define a concrete goals
         1. to focus
      2. James Whittaker Tours
         1. The Money tour
            1. Cover those features and functions that are highlighted in marketing literature
         2. The Landmark tour
            1. Navigate through an application
            2. Check list. UI-testing. Web-form. Font. Navigation
            3. https://www.xmind.net/m/qWtv/
         3. The Intellectual tour
            1. Needs to be asking the hardest questions
         4. The FedEx tour
            1. Needs to be able to track the data through the various stages as it flows through the app
         5. The After-hours tour
            1. Test maintenance functions
         6. The Garbage collector's tour
            1. Do a spot check on every item of a particular feature.
      3. James Bach & Michael Bolton Tours
         1. Documentation Tour:
            1. find user manual and some instructions
         2. Sample Data Tour:
            1. Employ any sample data you can
         3. Variability Tour:
            1. Tour a product looking for anything that is variable and vary it
         4. Complexity Tour
            1. Tour a product looking for the most complex features and data
         5. Continuous Use
            1. While testing, do not reset the system
         6. https://www.developsense.com/blog/2009/04/of-testing-tours-and-dashboards/
      4. Mike Kelly Tours
         1. FCC CUTS VIDS
            1. Feature tour
            2. get familiar with all the controls and features
            3. Complexity tour
            4. find the five most complex things about the app
            5. Claims tour
            6. find all the information in the product which tells you what the product does
            7. Configuration tour
            8. find all the ways you can change settings in the app
            9. User tour
            10. Imagine five users for the product and the information they would want from the product or the major features they would be interested in
            11. Testability tour
            12. find all the features you can use as testability features
            13. Scenario tour
            14. Imagine five realistic scenarios
            15. Variability tour
            16. :find things you can change in the application
            17. Interoperability tour
            18. What does this app interact with?
            19. Data tour
            20. Identify the major data elements of the app
            21. Structure tour
            22. Find everything you can about what comprises the physical product
4. Step 4
   1. Adapt brainstorm techniques
      1. Explore the product from different viewpoints
      2. The six Thinking Hats
         1. How to use the Six Thinking Hats for UX-Exploratory Testing
            1. https://www.xmind.net/m/cwwC/
5. It will be useful!
   1. Advice
      1. Try to focus exploratory testing on capabilities instead of features leads to deeper insights and prevents tunnel vision.
   2. Think about
      1. When should we stop testing?
         1. https://www.xmind.net/m/bLn2/
   3. Sourses
      1. https://testingtimes.com.au/exploratory-testing-references/
      2. https://ministryoftesting.com/dojo/lessons/explore-galore-30-tips-to-supercharge-your-exploratory-testing-efforts
      3. http://katrinatester.blogspot.com/2014/09/heuristics-and-oracles.html
      4. http://www.kaner.com/pdfs/QAIExploring.pdf
      5. http://www.satisfice.com/blog/archives/1509
      6. https://assets.ctfassets.net/ut4a3ciohj8i/4ukPUn6tfiig8S4ASuaeoQ/670bba8e5498239a7fbbf404952beb08/Ingo_Philipp_Rediscover_Exploratory_Testing.pdf
      7. https://www.xmind.net/m/7FMV/
      8. https://danieldonbavand.com/testing-166/
      9. https://searchsoftwarequality.techtarget.com/tip/Six-tours-for-exploratory-testing-the-business-district-of-your-application