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.