Home > Ask the Software Quality Experts > Software Testing and Quality Assurance Questions & Answers > Quality assurance testing vs. user acceptance testing
Ask The Software Quality Expert: Questions & Answers
EMAIL THIS

Quality assurance testing vs. user acceptance testing

Baher Malek EXPERT RESPONSE FROM: Baher Malek

Pose a Question
Other Software Quality Categories
Meet all Software Quality Experts
Become an Expert for this site


Software quality news and advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 22 October 2008
What is the difference between quality assurance testing and user acceptance testing?


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



RELATED CONTENT
Software Testing and Quality Assurance
Why do performance testers write new scripts so often?
How to create performance testing workload models
Fixing Web application performance troubleshooting problems
Expert advises on implementation of Selenium IDE for effective software testing
When should regression testing occur in an automated test plan?
Achieving peak performance in integration testing
Getting answers about OpenSTA script problems
Defining core software regression tests
Breaking in functionality on UI application pages
Where to find good methodology guides for software testing

User acceptance testing
Running user interface, unit and integration tests suites
How to improve software user acceptance testing practices
What is the best approach to generating a positive user experience?
Lieberman Enterprise Random Password Manager
AMD's AVX instruction set
Infragistics NetAdvantage for .NET
Ascentn's AgilePoint Developer
Features in Teamprise Client Suite 3.2
Parasoft SOA Quality Solution, SOAtest 6
JNBridge Pro 4.1

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


More information on user acceptance testing (UAT)
Don't mistake user acceptance testing for acceptance testing

User acceptance testing that satisfies users and requirements

User acceptance testing vs. system integration testing
The difference between quality assurance (QA) testing and user acceptance testing (UAT) varies across organizations and often within organizations. In general, UAT is usually the final testing process prior to deployment and is performed by a business tester who ultimately signs off on the product. The business tester attempts to execute relevant business scenarios to determine if the system as tested will satisfy the real-world business needs.

QA testing usually precedes UAT and is typically performed within the technology organization. QA testing examines the functional behavior of individual technology components and seeks to test their integrated feature-level capability. One of the constant challenges QA testing teams face is the wide variety of testing skills required to properly bridge technology testing with business testing. An effective QA test team is able to provide test at both a technical component level to enable early feedback, as well as at a scenario level to bridge with business users. One way to tackle that challenge is to develop a collaborative partnership with the business testing team that could consist of test development reviews, test data preparation, and paired test execution.

A summary of the typical differences between QA testing and UAT are as follows:


Although some say there should be strict isolation between the QA testing teams and user acceptance testing teams, more often than not this only defers important feedback and reduces the overall testing capability. When possible a collaborative testing process usually yields more defects earlier in the process, thereby giving the development team sufficient time to implement a fix and submit for retest.

The surest way to kill a project is to view testing as a "phase" that belongs at the end of a project as opposed to an integrated part of the ongoing development process. Waiting until the very end to start testing (either QA testing or user acceptance testing) will create problems for even the simplest of projects. An iterative and collaborative QA testing/user acceptance testing process can be a powerful tool for discovering issues early and providing forecasting data that helps to guide the project to a successful deployment.




Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Software Quality - Software Maintenance, Software Requirements, Software Standards
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2006 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts