Exploratory testing in Testing Fundamentals - Framework Patterns

Framework Mode - Exploratory testing

Folder Structure for Exploratory Testing Documentation

exploratory-testing-project/
├── charters/               
│   ├── login-feature.md
│   ├── payment-module.md
│   └── user-profile.md
├── session-notes/          
│   ├── session-2024-06-01.md
│   ├── session-2024-06-02.md
│   └── session-2024-06-03.md
├── bugs/                   
│   ├── bug-101.md
│   ├── bug-102.md
│   └── bug-103.md
├── tools/                  
│   └── screen-recorder-config.json
├── reports/                
│   └── june-summary.md
└── README.md               
  

Exploratory Testing Layers

• Charters Layer: Defines the goals or focus areas for each exploratory session. Helps testers stay focused.
• Session Notes Layer: Testers record observations, ideas, and bugs found during each session here.
• Bugs Layer: Document detailed bug reports discovered during exploratory testing.
• Tools Layer: Contains any supporting tools like screen recorders or note-taking templates.
• Reports Layer: Summarizes findings and insights from multiple exploratory sessions for stakeholders.

Configuration Patterns for Exploratory Testing

• Charter Templates: Use markdown templates to standardize how charters are written.
• Session Timing: Define session lengths (e.g., 60 minutes) to keep testing focused and manageable.
• Environment Setup: Document which environment (dev, staging) to use for exploratory testing to ensure consistency.
• Tool Settings: Configure screen recording or note-taking tools with default settings for easy use.
• Bug Reporting Guidelines: Provide a checklist or template to ensure bugs are reported clearly and consistently.

Test Reporting and CI/CD Integration

• Session Reports: After each session, testers write a summary report highlighting what was tested, bugs found, and ideas for further testing.
• Bug Tracking Integration: Link exploratory bugs to the main bug tracking system (e.g., Jira) for visibility and tracking.
• Regular Summaries: Create weekly or monthly reports summarizing exploratory testing progress and key findings.
• CI/CD Role: Exploratory testing is manual and does not run in CI/CD, but findings can inform automated test improvements.

Best Practices for Exploratory Testing Framework

• Define Clear Charters: Always start sessions with a clear goal to guide exploration and avoid randomness.
• Timebox Sessions: Limit session length to keep testers focused and avoid fatigue.
• Document Thoroughly: Keep detailed notes and bug reports to capture insights and reproduce issues later.
• Use Tools Wisely: Employ screen recording and note-taking tools to capture context without interrupting flow.
• Review and Share: Regularly review session notes and share findings with the team to improve product quality.

Self Check Question

Where would you add a new test charter for exploring the "Search" feature in this exploratory testing framework structure?

Key Result

Exploratory testing frameworks organize focused test charters, session notes, and bug reports to guide and document manual exploration effectively.

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