The scope of user acceptance testing
What is scope of user acceptance testing of software?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The scope of user acceptance testing varies greatly. Two key factors that affect scope include the time allocated and the technical expertise of the users executing the testing. Whether or not an application has been tested previously by a testing team before UAT is conducted might be a factor as well.

If time isn't allotted, UAT tends to be reduced. If the users don't advocate for more testing time or understand why they need the time or what other testing could be conducted, UAT can become a short and shallow cycle. If a testing team has tested the product, then the UAT cycle might be more of a signoff exercise.

Most of my experience with UAT has been more of a "feel good" activity.

User acceptance testing:
Don't mistake user acceptance testing for acceptance testing

User acceptance testing that satisfies users and requirements

Automating user acceptance test cases
Users often execute a handful of happy path scenarios and tend to be stumped about what else to test. In one situation, developers and members of the product team stayed in the room during UAT with the idea that they could answer questions for users. I think having the product team watch the users curbed the user testing.

If you're managing a testing team and have been asked to run or be involved with UAT, I would suggest spending time with the users to understand what they want and hope to gain from the experience. I wouldn't rely on UAT as a replacement to testing dedicated test resources offer.

This was first published in May 2008