Collaborating for Quality – Pair Testing
Software Quality Assurance is evolving day by day in terms of the tools and processes. QA Engineers often adopt new processes in to the Software Development Lifecycle to improve the quality. When we think of software testing, we probably imagine a single person sitting at his/her computer executing tests. Pair Testing changes the traditional way of testing, following up with multiple advantages including Defects Prevention.
What is Pair Testing?
It is a testing approach, which involves two individuals, usually a QA Engineer and a Developer. Apart from this combination, a QA Engineer can work with another QA Engineer, Business Analyst, Product Owner, Client or with a Marketing Person. The two individuals will work at the same computer executing a list of selected test scenarios to cover a feature or an enhancement. During the Pair Testing session, both can point out the defects, raise their concerns and give their feedback on the feature or enhancement.
How to do Pair Testing?
- Select a feature and determine the test scenarios
QA Engineer should select a feature that needs pair testing and should determine the important test scenarios to test it. These scenarios should consist of basic flows of the feature.
- Decide a time frame
Determine a time for Pair Testing that gives yourself enough room to explore the selected feature.
- Pair with the relevant person
Usually the person controlling the Pair Testing will be a QA Engineer and the other individual will be the developer who developed the respective feature. Apart from this combination, two QA engineers can pair to look at the feature in a different perspective.
- Prepare the environment
Pair Testing environment will be the development environment or a specific server set up to do Pair Testing.
- Take notes
Both parties should note down the defects found during Pair Testing as well as the concerns and feedback given by each other.
- Share the status
Share the status of your Pair Testing session with the stakeholders. This status should include the defects you have found during the testing, incomplete paths you have found and the enhancements that should be done.
Advantages of Pair Testing
- Defects prevention
The most important benefit of Pair Testing is defect prevention. If Pair Testing session is done in development environment or in a specific environment set up for Pair Testing, developer can fix the defects before the feature gets released to the testing environment.
- Saves time
Pair Testing session with a developer helps to identify the cause of defects quickly since they are familiar with the code. Re work effort and the defects tracking time will be saved as they are identified earlier.
- Two Perspectives
Pair testing provides the chance to look at the feature in two different perspectives. When a QA engineer combines with a Business Analyst, Product Owner, or a Client, it will generate valuable feedback on usability of the feature.
- Build up team collaboration
Pair testing helps to reduce the communication gaps between the team members and build up the collaboration as everyone of the team work for a common goal of producing quality software.
- Knowledge sharing
Pair Testing is a good way for each participant to learn from each other while providing quality output. When a new person joins the team, conducting Pair Testing will help them to get a good understanding on the product and its features.
- Efficient exploratory testing
While executing selected test scenarios, Pair Testing participants can spend some time on exploratory testing on the feature since working with someone from a different functional area improves the chances of discovering more defects.
As a conclusion, It’s very beneficial to implement Pair Testing within the Software Development Lifecycle as it builds quality based culture and ultimately it leads to client satisfaction.
The Who, What, When, and How of Pair Testing :
The Many Advantages of Pair Testing :