Exploratory testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Exploratory Testing

Which of the following best describes the main purpose of exploratory testing?

A To simultaneously learn about the software, design tests, and execute them without predefined scripts

B To follow a strict test script and record results exactly as written

C To automate all test cases for faster execution

D To only test the user interface without considering backend functionality

💡 Hint

Think about testing that involves learning and adapting as you go.

Exploratory testing is about learning the software while testing it, designing and executing tests on the fly without strict scripts.

🧠 Conceptual

intermediate

Key Skill for Exploratory Testers

Which skill is most important for a tester performing exploratory testing?

A Creativity and critical thinking to design tests on the fly

B Strong knowledge of automation tools

C Ability to write detailed test scripts before testing

D Expertise in coding unit tests

💡 Hint

Consider what helps testers adapt and find unexpected issues.

Creativity and critical thinking help testers explore the software and find defects not covered by scripts.

❓ assertion

advanced

Valid Assertion in Exploratory Testing Session

During an exploratory testing session, which assertion is most appropriate to check a login feature?

Testing Fundamentals

assert login_button.is_enabled()

A assert page_title == 404

B assert login_button.text == 'Logout'

C assert login_button.is_enabled()

D assert user_password == 'password123'

💡 Hint

Think about what confirms the login button is ready for user interaction.

Checking if the login button is enabled confirms the user can attempt to log in, which is a valid assertion.

🔧 Debug

advanced

Identifying Issue in Exploratory Testing Notes

A tester notes: 'Clicked submit, no response, no error message.' What is the best next step?

A Ignore the issue since no error message appeared

B Restart the application without further investigation

C Assume the feature works fine and move on

D Check the network requests and console logs for hidden errors

💡 Hint

Think about how to find hidden problems when the UI shows no feedback.

Checking network and console logs helps find errors not visible in the UI, aiding exploratory testing.

❓ framework

expert

Best Practice for Documenting Exploratory Testing

Which approach best supports documenting exploratory testing sessions for future reference?

A Write detailed test cases before starting exploratory testing

B Record session notes including test ideas, observations, and defects found during the session

C Only document defects after the session ends

D Avoid documentation to keep testing spontaneous

💡 Hint

Think about capturing what you learn and find during testing.

Recording notes during exploratory testing helps track what was tested, what was found, and supports reproducibility.

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