Exploratory testing

Types of testing

  • Ad-hoc testing is an informal, which you can perform without predefined test cases and test plan, not structured, you may find critical bugs missed by automated or regression testing.
  • Scripted testing = testing by already documented tests (we have steps to reproduce), test cases are created, then follow them to verify the actual results.
  • Exploratory testing = is about learning product simultaneously and designing test cases (executing them) and creating test plan.

Experience based testing

Mostly used in agile teams.

Types:

  1. Error guessing = guessing where the error might be.
  2. Checklist based testing = a checklist of different functionalities and use cases for testing.
  3. Exploratory testing

      4. What helps to make an exploratory testing?

    1. Experience of tester = operations of some products are the same ( authentication)
    2. Intuition
    3. Error guessing = test design technique based on experience

      4. Exploratory testing (how to get an experience):

    4. + Cheat sheet (to create test cases)
      • Negative and positive, general and internal, by types of testing
    5. + Tour testing
    6. ~ Session based technique
    7. - Pair testing

How to execute exploratory tests?

  1. Create a bugs classification → categorize common types of faults found in the past projects. Find risks and develop ideas
  2. Create test charter → what to test, how it can be tested, expected result (acceptance criteria)

    3. Test charter helps determine how the end user could use the system

  3. Time box - work for 90 minutes with a pair of testers
  4. Review Result → evaluation of the defects, analysis of coverage areas

Advantages of exploratory testing

  • This testing is useful when requirement documents are not available or partially available. Tester might find more bugs.
  • Encourages creativity and intuition.
  • Approaching high-pressure deadlines

Disadvantages of exploratory testing

  • This testing purely depends on the tester skills
  • Limited by domain knowledge of the tester
  • Not suitable for long execution time
  • A poor basis for introducing test automation
  • Overlapping tests

Detailed test cases

💥The MOST comprehensive testing checklist and practices

References

SuperMade with Super