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.

Practice

1. What is the main idea behind pair testing in software testing?

easy

A. Testers work in pairs but test different features independently.

B. Two testers work separately on different devices to compare results.

C. Two testers work together on one device to find bugs faster.

D. One tester writes tests while the other writes code.

Solution

1. Step 1: Understand the definition of pair testing and compare options

   Pair testing means two testers work together on one device to collaborate closely. "Two testers work together on one device to find bugs faster." correctly describes this.

2. Final Answer:

   Two testers work together on one device to find bugs faster. -> Option C

3. Quick Check:

   Pair testing = Two testers, one device [OK]

Hint: Pair testing means two testers share one device [OK]

Common Mistakes:

• Thinking testers work separately in pair testing
• Confusing pair testing with pair programming
• Assuming testers test different features independently

2. Which of the following is the correct way to describe the roles in pair testing?

easy

A. Testers switch roles often to keep both active and engaged.

B. One tester tests while the other watches silently without switching roles.

C. Testers work independently and combine results at the end.

D. One tester writes bugs, the other fixes them immediately.

Solution

1. Step 1: Recall role behavior in pair testing and match options

   In pair testing, testers switch roles often to stay active and share knowledge. "Testers switch roles often to keep both active and engaged." correctly states this.

2. Final Answer:

   Testers switch roles often to keep both active and engaged. -> Option A

3. Quick Check:

   Role switching = Active testers [OK]

Hint: Roles switch often in pair testing to stay engaged [OK]

Common Mistakes:

• Assuming one tester is passive
• Thinking testers work independently
• Confusing pair testing with bug fixing roles

3. Consider this scenario: Two testers are pair testing a login feature. Tester A types inputs while Tester B observes and suggests test cases. What is the main benefit of this approach?

medium

A. It allows testers to work on different features simultaneously.

B. It reduces the total number of test cases needed.

C. It ensures only one tester is responsible for bugs.

D. It helps find bugs faster and shares knowledge between testers.

Solution

1. Step 1: Analyze the pair testing scenario and identify the benefit

   Tester A inputs data, Tester B observes and suggests test cases, showing collaboration. This helps find bugs faster and shares knowledge between testers.

2. Final Answer:

   It helps find bugs faster and shares knowledge between testers. -> Option D

3. Quick Check:

   Pair testing benefit = Faster bugs + knowledge sharing [OK]

Hint: Pair testing speeds bug finding and knowledge sharing [OK]

Common Mistakes:

• Thinking it reduces test cases
• Believing only one tester is responsible
• Assuming testers work on different features

4. During pair testing, a team notices that one tester is always controlling the device and the other rarely participates. What is the main problem here?

medium

A. The testers are not switching roles often, reducing engagement.

B. The device is faulty and causing delays.

C. Testers should work independently to be efficient.

D. One tester should write code while the other tests.

Solution

1. Step 1: Identify the issue in pair testing and its impact

   One tester always controls the device, meaning roles are not switching often. This reduces engagement and knowledge sharing.

2. Final Answer:

   The testers are not switching roles often, reducing engagement. -> Option A

3. Quick Check:

   No role switching = Low engagement [OK]

Hint: Lack of role switching reduces tester engagement [OK]

Common Mistakes:

• Blaming the device instead of process
• Suggesting independent work in pair testing
• Confusing testing roles with coding roles

5. You are asked to improve the efficiency of pair testing for a complex feature. Which approach best applies pair testing principles to maximize bug detection and knowledge sharing?

hard

A. Have two testers test separately and merge their bug reports at the end of the day.

B. Assign two testers to work together on one device, switching roles every 15 minutes, discussing findings continuously.

C. One tester tests while the other documents test cases without switching roles.

D. Testers take turns testing different features independently to cover more ground.

Solution

1. Step 1: Identify key pair testing principles and evaluate options

   Pair testing: two testers on one device, switch roles often, share knowledge. "Assign two testers to work together on one device, switching roles every 15 minutes, discussing findings continuously." matches all.

2. Final Answer:

   Assign two testers to work together on one device, switching roles every 15 minutes, discussing findings continuously. -> Option B

3. Quick Check:

   Pair testing best practice = Together + switch roles + discuss [OK]

Hint: Switch roles often and discuss to maximize pair testing [OK]

Common Mistakes:

• Testing separately instead of together
• Not switching roles during testing
• Ignoring communication between testers