In particular, after a weekend testing session where remote pairing was a hard experience to deliver through writing and instructions, I asked people from that group to give me an hour to experience it with me.
The setup for pairing was use of my computer, sharing control of it through join.me -application. We would have a Mindmup-document to make notes on. We would have Dark Function Editor as out system under test. And we would have a recon mission, learning what there is that should be tested as our starting task. And we would change who was driving (using keyboard) and navigating (speaking of what to do) every four minutes.
The four sessions I had were completely different in how they felt to do as a pair. The four sessions also had very different outcomes as in the learnings we had on the application within that timeframe.
- She made me work on higher level of abstraction, giving me small tasks without details on instruction with instant feedback on correcting if I misinterpreted what she wanted
- We noticed things together, and found bugs in the application I had not seen here
- She knew what she was doing, even if she usually tests backend and logs.
- Very focused on what is a bug and knowing the right answer on a product we don't know made me feel like my product, even me, was being criticized.
- Strong assumptions, not testing for what is plausible out of what we think we already know; overconfidence in coverage in short time
- Not staying with the pair but going alone to prepare the data - different idea of working in pair
- As a driver I keep asking "what would you like me to do", "did you notice", "should we make a note of that" - feeling left out.
- Could not change roles while "in middle of something".
- Pointed out a type of functionality I had not paid attention to before: tabs.
- Not "pairing" but "working individually with someone watching".
- Needs longer timeframe to build into collaboration not a skills demo.