• Home
  • RSS Feed
  • Log in

Paired Testing
Posted by Aman Arora just before lunchtime: September 30th, 2009

Nowadays paired programming concept is getting more and more common in the IT industry because of its benefits like design quality, overcoming difficult problems and better time management etc. Similarly a new concept of Paired Testing is getting famous now among the testers who are working in an agile environment. This concept of testing is similar to paired programming approach. In this approach the person doing the testing is called the driver while the other suggests ideas or tests, pays attention and takes notes, listens, asks questions, grabs reference material, observes or reviews etc.

Paired testing can be really helpful when a new team member has joined the team and the project is in the middle of the sprints. A team member who is mature enough and have a good knowledge about the application can then be taken as a driver making the new team member as a observer so that he can learn the functionality.

Paired testing can be started with defining of a charter which include what to test, what tools to use, what testing tactics to use, what risks are involved, what bugs to look for, what documents to examine, what outputs are desired, etc. and can be ended once the reports are generated which can have the defect numbers that were logged while doing the testing.

Benefits of Paired Testing

  • Idea generation, as the testers are working in a pair so one can really come up with new ideas while the other is implementing the same.
  • Switching of roles, if one of the tester is tired of doing the testing so they can switch the roles and then start doing the testing again.
  • Helps the tester stay on task.
  • Restricts the interruption, when 2 testers are working together it limits others to interrupt them which increases the productivity.
  • Defect reproducibility, bugs can be easily reproducible as while doing the exploratory testing alone a tester tends to forget the steps due to which the defect occurred.
  • Good learning platform, paired testing gives a good learning platform if a new tester has joined the team.

Drawbacks of Paired Testing

  • Paired testing can be a big failure if the pair doesn't share the mutual understanding.
  • If both the members are not mature enough.
  • If both the members are new to the application or to the paired testing concept.
  • Share/Bookmark

Filed under Testing | 2 Comments »



2 Responses to “Paired Testing”



    Sanjeev Says:
    Posted at: October 30, 2009 at 6:01 pm

    Seems an interesting concept, a formal methodology like this can improve testing as well.



    Aman Says:
    Posted at: November 2, 2009 at 5:21 am

    Thanks for the response, it will be great if you can share your thoughts too.



Leave a Reply

Click here to cancel reply.

Deployment automation for Java application running on Websphere, WebLogic and JBoss

Categories

  • Java (291)
  • Agile (127)
  • General (96)
  • Architecture (47)
  • Testing (45)
  • Scrum (44)
  • Performance (42)
  • Podcast (31)
  • SOA (25)
  • Middleware (31)
    • Deployment (20)
  • Project Management (23)
  • Xebia Labs (21)
  • Quality Assurance (16)
  • Tools (12)
  • lean architecture (11)
  • Requirements Management (10)
  • Articles (9)
  • Virtualization (9)
  • Security (7)

Tag Cloud

    Moving to India websphere Hibernate Ajax IntelliJ Maven Scala Concurrency Control qcon XML Scrum Frameworks SOA Agile Grails JPA Oracle Flex JPA implementation patterns Performance Eclipse lean architectuur Lean lean architecture agile architectuur Java Spring Groovy ACT Architecture

Xebia Sites

  • Xebia Corporate
  • Xebia France
  • Xebia India

Archives

  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009