HERE

Making User Acceptance Testing Less Painful

User Acceptance Testing (UAT) is a powerful form of testing that is essential in gaining end user buy-in for new products or new features and enhancements.  However, UAT is often too time consuming and difficult to manage to be leveraged to its full potential. qTest eXplorer provides a new and simpler approach to UAT. eXplorer is a test documentation tool that is simple to use and automatically captures rich, detailed documentation from UAT sessions – allowing you to conduct UAT more frequently and gather more valuable input from the end users.

User Acceptance Testing (UAT) is a powerful form of testing that is essential in gaining end user buy-in for new products or new features and enhancements.  However, UAT is often too time consuming and difficult to manage to be leveraged to its full potential.

Though UAT is widely accepted in the testing community as a valuable form of gaining end user feedback and acceptance of a product before launch, it is notoriously difficult to manage efficiently.  Given the lack of testing experience of the Subject Matter Experts (SME’s) that are typically tasked with performing UAT, there is a great need for a way to simplify preparation, execution, and post-processing of this essential testing cycle.  QASymphony’s qTest eXplorer is an innovative tool that allows inexperienced testers to quickly and accurately record and report their feedback.  The tool cuts the time spent in these areas by more than half, allowing you to perform UAT more frequently and to receive more detailed insight from the UAT cycles already being performed.

The major challenges of managing UAT usually present themselves within one of three phases of UAT: preparation, execution, and post processing.  QASymphony aims to provide a tool that can help along every step of the process.

QASymphony’s qTest eXplorer cuts the time spent in these areas by more than half, allowing you to perform UAT more frequently and to receive more detailed insight from the UAT cycles already being performed.

Preparation

What’s involved: Creating detailed test cases for UAT testers to execute.

Challenge(s) facedGenerating test cases with enough direction that UAT testers who may not have been involved in requirements gathering or design sessions can understand them.  Additionally, finding the bandwidth to create these test cases during cycle closeout, which is typically one of the busiest times for testers.

How eXplorer helpsProviding detailed screenshots as well as plain text narration of the steps performed within the application.  This way, testers can quickly generate UAT test scripts simply by walking through the application, rather than writing them by hand – reducing test case creation time by up to 50% or more.

Execution

What’s involved: Training UAT testers on how to properly document defects for submission to developers.

Challenge(s) faced:Finding the time to train UAT testers on the testing process and tools, as they are usually on “borrowed time” from the business.  Also, ensuring that these testers provide the appropriate level of detail required to document a defect.  This additional information helps developers speed up the process of debugging a defect.  Otherwise, a tester may need to look over the SME’s shoulder to make sure that relevant and detailed defects are submitted.

How eXplorer helps: eXplorer’s simple interface helps UAT testers quickly pick up and learn the tool.  The simple note-taking tool combined with automated recording ensures that UAT testers provide detailed feedback without taking much of their time.  Furthermore, qTest standardizes the information submitted within defects, so SME’s defects are as easy for developers to understand and reproduce as any other defects.

Post Processing

What’s involved: Gathering and organizing feedback from UAT test sessions to discern any areas that must be fixed before promoting new features into production.

Challenge(s) faced:Ensuring that all feedback submitted by UAT testers is properly organized and logged within the defect tracking tool.  Additionally, ensuring feedback provided is truly a defect rather than a misunderstanding of the application’s design.

How eXplorer helps: Seamless integrations with the most popular bug trackers to ensure that defects are properly organized and required fields are filled out.  Also, standardization of screen names and inclusion of URL’s where bugs were found (for web applications) so it is easy to determine the exact artifact where the defect was logged.

In short, UAT is a critical testing phase that provides its own unique challenges to the SME’s and testers alike.  Existing test case management systems and other UAT test management tools are cumbersome and complex, making UAT testing a complex process reserved only for critical phases of a project.  qTest eXplorer removes the traditional headaches and obstacles of managing UAT and allows your SME’s to perform more testing and provide more detailed and valuable insight.  With the simpler process, you can conduct UAT more regularly and be able to take advantage of this great technique to shorten the development time and deliver software that better meets the needs of the end users.

Want to put qTest eXplorer to the test during your next round of UAT?  Try it out here  for 30-days for free!

1 comment on Making User Acceptance Testing Less Painful

  1. Carl Johnson says:

    thanks

Leave a Reply

Your email address will not be published. Required fields are marked *

More Great Content

Get Started with QASymphony