Exploratory testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is exploratory testing?

Exploratory testing is a way to test software by exploring it freely without following a fixed script. Testers learn and test at the same time.

beginner

How does exploratory testing differ from scripted testing?

Scripted testing follows pre-written steps, while exploratory testing is flexible and adapts as testers discover new things.

intermediate

Name one key skill needed for effective exploratory testing.

Good observation skills help testers notice unexpected behavior and find hidden bugs during exploratory testing.

intermediate

Why is exploratory testing useful in agile development?

Because agile changes quickly, exploratory testing helps testers adapt and find issues without waiting for detailed test cases.

intermediate

What is a common tool or technique used to support exploratory testing?

Session-based testing is a technique where testers set a time box to explore and record what they test and find.

What is the main characteristic of exploratory testing?

A Following detailed test scripts

B Testing without any plan or goal

C Simultaneous learning, test design, and execution

D Only testing the user interface

Exploratory testing involves learning about the software, designing tests, and executing them all at the same time.

Which of the following is NOT a benefit of exploratory testing?

A Requires no tester skills

B Adapts well to changing software

C Finding unexpected bugs quickly

D Encourages tester creativity

Exploratory testing requires skilled testers who can think critically and observe carefully.

In exploratory testing, what is a 'session'?

A A time-boxed period of focused testing

B A fixed set of test cases

C A meeting to discuss bugs

D A software installation process

A session is a set time where testers explore the software and document their findings.

Which approach best describes exploratory testing?

A Testers follow a checklist strictly

B Testers only test what developers say

C Testers automate all tests

D Testers explore and learn while testing

Exploratory testing is about exploring and learning during the test process.

When is exploratory testing especially useful?

A When detailed test scripts are ready

B When requirements are unclear or changing

C When testing is fully automated

D When testing only backend APIs

Exploratory testing helps when requirements are unclear or change often, allowing testers to adapt quickly.

Explain exploratory testing and why it is important in software testing.

Think about how testers learn and test at the same time without fixed scripts.

Describe how session-based testing supports exploratory testing.

Consider how testers manage their time and document their work during exploration.

Practice

1. What is the main goal of exploratory testing?

easy

A. To find bugs by freely exploring the software

B. To write detailed test scripts before testing

C. To automate all test cases

D. To test only the user interface

Solution

1. Step 1: Understand exploratory testing purpose

   Exploratory testing means testing without fixed scripts, exploring freely to find bugs.

2. Step 2: Compare options with definition

   Only To find bugs by freely exploring the software matches this idea; others describe scripted or automated testing.

3. Final Answer:

   To find bugs by freely exploring the software -> Option A

4. Quick Check:

   Exploratory testing = find bugs freely [OK]

Hint: Exploratory means exploring freely to find bugs [OK]

Common Mistakes:

• Confusing exploratory with scripted testing
• Thinking exploratory is only automation
• Believing it tests only UI

2. Which of the following is a correct practice during exploratory testing?

easy

A. Following a strict test script without deviation

B. Avoiding any note-taking during testing

C. Only testing features that have detailed requirements

D. Using creativity to try different actions in the software

Solution

1. Step 1: Identify exploratory testing practices

   Exploratory testing encourages creativity and trying different actions freely.

2. Step 2: Evaluate each option

   Using creativity to try different actions in the software fits this; others restrict testing or avoid useful habits like note-taking.

3. Final Answer:

   Using creativity to try different actions in the software -> Option D

4. Quick Check:

   Creativity = exploratory testing [OK]

Hint: Creativity and freedom are key in exploratory testing [OK]

Common Mistakes:

• Thinking exploratory testing requires strict scripts
• Ignoring features without detailed requirements
• Not taking notes during testing

3. During exploratory testing, a tester tries to log in with invalid credentials multiple times. What is the expected outcome?

medium

A. The system crashes immediately

B. The system allows login without error

C. The system blocks login and shows an error message

D. The system logs in with default admin access

Solution

1. Step 1: Understand login behavior with invalid credentials

   Systems usually block login attempts with wrong credentials and show error messages.

2. Step 2: Match expected behavior with options

   The system blocks login and shows an error message matches expected behavior; others describe incorrect or unsafe outcomes.

3. Final Answer:

   The system blocks login and shows an error message -> Option C

4. Quick Check:

   Invalid login = error message [OK]

Hint: Invalid login should show error, not allow access [OK]

Common Mistakes:

• Assuming system crashes on invalid login
• Thinking invalid login grants admin access
• Believing system ignores invalid attempts

4. A tester performing exploratory testing notices the app crashes when clicking a button, but the crash is not reproducible every time. What should the tester do?

medium

A. Report the crash with detailed steps and environment info

B. Assume the crash is caused by user error and do nothing

C. Ignore it since it is not consistent

D. Restart the app and continue testing without reporting

Solution

1. Step 1: Understand handling intermittent crashes in exploratory testing

   Even if a crash is not consistent, it should be reported with details to help developers.

2. Step 2: Evaluate options for best practice

   Report the crash with detailed steps and environment info is correct; ignoring or assuming user error is bad practice.

3. Final Answer:

   Report the crash with detailed steps and environment info -> Option A

4. Quick Check:

   Report all crashes with details [OK]

Hint: Always report crashes with details, even if intermittent [OK]

Common Mistakes:

• Ignoring intermittent bugs
• Assuming user error without evidence
• Not providing environment info in reports

5. You are doing exploratory testing on a new app with unclear requirements. Which approach best helps you find important bugs quickly?

hard

A. Randomly click everywhere without any plan

B. Use your knowledge to explore critical areas and take notes

C. Focus only on features with written requirements

D. Wait for developers to provide test cases

Solution

1. Step 1: Identify best exploratory testing approach with unclear requirements

   Exploratory testing works best by using tester's knowledge to explore important areas thoughtfully.

2. Step 2: Compare options for effectiveness

   Use your knowledge to explore critical areas and take notes uses knowledge and notes, which is best; random clicking or waiting wastes time.

3. Final Answer:

   Use your knowledge to explore critical areas and take notes -> Option B

4. Quick Check:

   Knowledge + notes = effective exploratory testing [OK]

Hint: Explore smartly using knowledge and notes, not random clicks [OK]

Common Mistakes:

• Testing only documented features
• Clicking randomly without focus
• Waiting passively for test cases