pair test

   In fact, I have been exposed to the concept of pair testing very early, but have not practiced it in specific projects. In today's brief summary, most of them are the results of previous searches from the website, and some of my own understandings have also been added. I will summarize it after the actual combat in the first and second quarters of 2013.

Some Thoughts on Pair Testing:

What is Pair Testing?
When developers are all concerned about pair programming, what should testers pay attention to? How to solve the problem of test omission caused by single-person testing (the main reason),
how to solve the problem of insufficient testing resources, and pair testing Woolen cloth? Pair testing is a technique in software development that allows two people in a team to test a product together, with
one tester actually operating the test product and the other tester analyzing or reviewing the test process and test results.

Why Pair Testing?
Briefly explain the advantages of paired testing:
a. Reducing test omissions: differences in work experience, educational experience, perspectives on problems, and ways of thinking will definitely allow us to take advantage of each other and complement each other when testing the same test sample. Reduce test omissions.
Each tester will have his own blind spot of thinking, and it is impossible for two people to have a common blind spot. In this way, the intersection of the blind spots of the two people's common testing thinking will become less, and the two people will be inspired together, and the test ideas will be more, and the
test will be missed . will be less.
b. Sharing of testing resources: Through resource sharing, the preparation of testing resources can be reduced
. c. To avoid the phenomenon of test fatigue: 2 people pair test together, they can jointly overcome the difficulties encountered and share the sense of achievement of finding defects, and the work will become More fun and more efficient.
d. Improve tester skills: sharing of test ideas and test methods during the test process, two people actually learn from each other, which will be helpful to everyone
e. Conducive to the equal distribution of workload: when a tester tests a module, sometimes there are fewer test tasks, and sometimes there are more test tasks. Two testers test two modules, and
the probability that both modules have more tasks is very small. When one module has more testing tasks and the other has fewer tasks, the work pressure of these two testing tasks will not be paired. It was so big before.
f. Better risk response: More testers are familiar with more test object functions, avoiding the risk of personnel turnover
g. Can the test progress be advanced? Personal feeling can be improved, and the specific improvement needs to be proved by practice.


How to do a pair test?
The prerequisites for the successful implementation of pair testing are as follows:
(1) At least one tester can be trusted and can test without guidance.
(2) Another tester needs to be involved in the test design process.
(3) The two testers must have the ability and mentality to work together.
Steps for pair testing:
(1) Choose a suitable partner for pair testing
//It is best to use old employees with new employees

(2) Select and establish a suitable pair testing environment
(3) Plan the time span of the test, define the scope of the test, test Concerns, test objectives, test outputs, etc., are similar to the test charter in exploratory testing;
//The testing scope and concerns can adopt the idea of ​​risk testing to determine the most risky modules, and pair testing will be more meaningful

( 4) Sessions in which paired tests are performed: one person leads, the other assists. Note that the testing process requires constant discussion of test scenarios, test questions, etc.;
(5) Evaluate the results of the pairing test: evaluate the problems found, the efficiency and effectiveness of the pairing test, unresolved problems, the next session's Plans etc.

Variants of Pair Testing
1. In fact, there can be more than 2 people testing, and multiple testing can be called team testing
2. The pairing test mentioned above is actually more about the pairing of the test process execution. In fact, there can also be principles to learn pairing, design pairing, etc.
3. Pairing test is not necessarily, two people must share information in real time, two people can jointly test different sub-modules of a module, a certain time span,
such as half a day or a day later for the following discussion