-
What?
-
Kind of exploratory testing
- Informal approach to explore the product
- Questioning the product
-
Two people work together
- From different background and knowledge
- Helps in iterative process
- An approach - not technique
-
Why?
- Different view of developer and BA
- Tester can help with techniques to test
-
How to do?
-
Find the pair
- Be a driver or navigator
-
Setup env
- No disturbance
- Timing
- Backlog
- Prioritization
-
Know requirement
- Scope of the test
- Target
-
Time duration/Schedule meeting
- No one disturb you
-
Determine goals
- Identify risks
- Mind map
- Express clearly
- Create test ideas
- Document
- Should not be like senior/junior partiality
-
Benefits
-
Knowledge transfer
- Dev/Tester
- BA/Tester
- New Tester/SME Tester
-
Identify more bugs
- Bugs are reviewed automatically
- Immediate bug fix if work with dev
- Saves time
- Fun/good relationship/communication
- Training other employees
- Breakdown barriers
- Gather more information
- New ideas
-
Why should avoid?
- No right env setup
-
Two people are not on good terms
- No win/lose
- To execute structured test case
-
How to conclude?
- Documentation
- Bug reporting