This document discusses exploratory testing. It defines exploratory testing as testing where the tester actively designs tests during the testing process and uses information gained from testing to design new tests. Key aspects of exploratory testing include investigation, discovery, learning, and using imagination to think of new tests. The document outlines what makes an excellent exploratory tester, the differences between exploratory and traditional scripted testing, pros and cons of exploratory testing, how to perform exploratory testing using techniques like the "tour bus principle", and myths about exploratory testing.

1. Exploratory Testing

2. Agenda
• What is exploratory testing?
• What makes you an excellent Exploratory Tester?
• Diff b/n exploratory testing & traditional testing
• Pros & Cons
• How to perform?
• Myths

3. What is Exploratory Testing?
• It is **not** a RANDOM testing. It’s a structured testing.
• It needs a conscious plan, but not a rigorous plan!
• Exploratory testing is
– Test Design and Test Execution at the same time.
– Discovery, Investigation and Learning
– A “thinking” activity
• Any testing that
– Tester actively controls the design of the tests during the testing phase
– Uses information gained while testing to design new and better tests.
• The richness of this process is only limited by the breadth and depth of
our imagination and our insights into the product under test
• There are no defined formulas for Exploratory testing.
– It depends on the individual when to declare the testing is complete.
– Test manager TRUSTS the individual and leave the choice to him/her.

4. What makes you an excellent
Exploratory Tester?
• Good at Test Design
• Careful Observation:
– Do not limit yourself to the test cases alone.(This is true for traditional
testing as well)
– Must watch for anything unusual or mysterious
• Critical Thinking
– Observation, Interpretation, Analysis etc…
• Diverse Ideas
• Previous knowledge on similar systems
• Determination
• Dedication

5. Differences
Scripted Testing Exploratory Testing
Directed from requirements Directed from requirements and exploring
during testing
Determination of test cases well in advance Determination of test cases during testing
Confirmation of testing with the
requirements
Investigation of system or application
Involves confirmed testing Involves Investigation
Is about Controlling tests Is about Improvement of test design
Like making a speech - you read from a
draft
Like making a conversation - its spontaneous

6. Pros & Cons
Pros Cons
This testing is useful when requirement documents are not
available or partially available
This testing purely depends on the tester skills
It involves Investigation process which helps find more bugs
than normal testing-
Limited by domain knowledge of the tester
Uncover bugs which are normally ignored by other testing
techniques
Not suitable for Long execution time
Helps to expand the imagination of testers by executing more
and more test cases which finally improves productivity as well
This testing drill down to smallest part of application and covers
all the requirements
This testing covers all the types of testing and it covers various
scenarios and cases
Encourages creativity and intuition
Generation of new ideas during test execution

7. How to perform
• Come up with an excel sheet/mind map with the list of high level scenarios
• Write down test ideas and use them in later test cycles.
• Think ->what’s the best test I can perform, right now?
• Time is limited
– Have a general plan of attack.
– So, allocate time for each scenario, prioritize.
– Slight deviations are allowed, but should keep an eye on the overall time spent/allocated for a
module.
• Keep a book & Pen with you( Don’t laugh, it works  )
– Write down all the new ideas that you get.
– Don’t simply depend on your memory
• There shouldn’t be too many interrupts for testing. Focus… focus.. focus….
• Make a note of all the issues ; Report them; Track them.
• Do not assume things. Ask…

8. Tour Bus Principle
• Even people on a tour bus get to step off it occasionally and
wander around. The key is not to miss the tour entirely, Nor to
fall asleep on the bus
• Apply this in your testing:
– Come up with an initial plan – High level scenarios
– Estimate individual modules/scenarios
– Explore certain module come up with test cases
– Start testing
– Add new ideas, tests that you get during your testing(Write it on to a
paper/excel sheet immediately)
– Allow slight deviations, but do not go off the track for a longer
duration.

9. Myths
• I don’t need to write test cases 
• No documentation -> No guarantee to test all
components?
• Exploratory testing is Random testing &
unstructured