Pair testing in Testing Fundamentals - Framework Patterns

Framework Mode - Pair testing

Folder Structure for Pair Testing Sessions

pair-testing-project/
├── session-notes/
│   ├── 2024-06-01-login-feature.md
│   ├── 2024-06-02-shopping-cart.md
│   └── README.md
├── test-scripts/
│   ├── login-tests.js
│   ├── cart-tests.js
│   └── utils.js
├── tools/
│   ├── screen-recorder.sh
│   └── timer.js
├── reports/
│   ├── 2024-06-01-report.html
│   └── 2024-06-02-report.html
└── README.md
  

This simple structure supports collaborative testing sessions by organizing notes, scripts, tools, and reports clearly.

Test Framework Layers in Pair Testing

• Session Notes Layer: Documents observations, ideas, and bugs found during the paired session.
• Test Scripts Layer: Contains automated or manual test scripts created or refined during the session.
• Tools Layer: Includes utilities like screen recorders, timers, or collaboration aids to support the pair.
• Reports Layer: Stores session summaries and test results for review and learning.

Pair testing focuses on collaboration, so layers emphasize shared documentation and communication.

Configuration Patterns for Pair Testing

• Environment Setup: Use shared environments or virtual machines so both testers see the same system state.
• Session Scheduling: Maintain a calendar or schedule file to plan pair testing times and topics.
• Access Credentials: Store credentials securely and share them with the pair to avoid delays.
• Tool Configuration: Configure screen sharing, recording, and note-taking tools before sessions.

Configurations focus on smooth collaboration and minimizing setup friction.

Test Reporting and CI/CD Integration in Pair Testing

• Session Reports: Create simple markdown or HTML reports summarizing findings and next steps.
• Bug Tracking: Log bugs found during sessions immediately into a shared bug tracker.
• CI/CD Integration: While pair testing is often manual, automated tests created can be integrated into CI pipelines.
• Feedback Loop: Share reports with the team to improve product quality and testing approaches.

Reporting emphasizes clear communication and quick sharing of insights.

Best Practices for Pair Testing Frameworks

1. Collaborative Note Taking: Use shared documents or tools so both testers contribute and review notes in real time.
2. Clear Role Switching: Alternate roles between driver (controls system) and navigator (observes and suggests) to keep both engaged.
3. Use Simple Tools: Keep tools lightweight and easy to use to avoid distractions during sessions.
4. Document Findings Immediately: Capture bugs and ideas as they happen to avoid forgetting details.
5. Review and Reflect: After sessions, review notes and reports together to plan next steps and improve testing.

Self Check Question

Where in this folder structure would you add a new note about a bug found during a pair testing session on the payment feature?

Key Result

Pair testing frameworks focus on collaboration through shared notes, simple tools, and clear communication.