Bird
Raised Fist0
Testing Fundamentalstesting~10 mins

Exploratory testing in Testing Fundamentals - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to start an exploratory testing session by setting the session time.

Testing Fundamentals
session_time = [1]  # time in minutes for exploratory testing
Drag options to blanks, or click blank then click option'
A60
B30
C120
D15
Attempts:
3 left
💡 Hint
Common Mistakes
Choosing too short or too long session times that reduce effectiveness.
2fill in blank
medium

Complete the code to log notes during an exploratory testing session.

Testing Fundamentals
notes = []
notes.[1]('Found a UI glitch on login screen')
Drag options to blanks, or click blank then click option'
Aclear
Bremove
Cpop
Dappend
Attempts:
3 left
💡 Hint
Common Mistakes
Using methods that remove or clear notes instead of adding.
3fill in blank
hard

Fix the error in the code that checks if a bug report is empty during exploratory testing.

Testing Fundamentals
if len(bug_report) [1] 0:
    print('Bug report is empty')
Drag options to blanks, or click blank then click option'
A!=
B=
C==
D<
Attempts:
3 left
💡 Hint
Common Mistakes
Using assignment operator = instead of comparison ==.
4fill in blank
hard

Fill both blanks to filter exploratory test notes that contain the word 'error' and convert them to uppercase.

Testing Fundamentals
filtered_notes = [note.[1]() for note in notes if 'error' [2] note]
Drag options to blanks, or click blank then click option'
Aupper
Bin
Cnot in
Dlower
Attempts:
3 left
💡 Hint
Common Mistakes
Using lower() instead of upper().
Using not in which filters out notes with 'error'.
5fill in blank
hard

Fill all four blanks to create a dictionary summarizing bug counts by severity from exploratory testing results.

Testing Fundamentals
bug_summary = {severity: [1] for severity, bugs in bug_data.items() if [2] > 0}
Drag options to blanks, or click blank then click option'
A{
Blen(bugs)
Cseverity
D}
Attempts:
3 left
💡 Hint
Common Mistakes
Using parentheses instead of braces for dictionary.
Not filtering severities with zero bugs.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard