UAT – The Guide (User Acceptance Test Engineering Guidance - Beta)

CodePlex - patterns & practices Acceptance Test Engineering Guidance

“…

Project Description

The Acceptance Test Engineering Guide will provide guidance for technology stakeholders (developers, development leads, testers, test leads, architects, etc.) and business stakeholders (managers, customers, end users, etc) on the discipline of acceptance testing.

Why acceptance testing?

patterns & practices has produced just a few guides related to testing (including performance testing, security testing of web apps, and testing of .NET application blocks). However, we hear a lot of requests from our customers for guidance on testing and test strategy in general, and also guidance on every type of testing you can think of. Based on this customer feedback, and a look at what guidance was available, we determined that acceptance testing was the next area to invest in.

What is acceptance testing?

Working definitions for a number of terms are available in our Draft Glossary. The current definition that is framing our work and discussions is:

• Acceptance Testing: Planned evaluation of a system by customers/customer proxies to assess to what degree it satisfies their expectations.

…

What types of things you can learn in the guide?

If any of the following goals apply to you, you will want to check out the the guide.

…”

I don’t know near enough about “real” UAT and as I’m trying to increase our QA depth at work, this guide may come in handy…

(via The Liquidator - Acceptance Test Engineering Guide (BETA1) – From Codeplex)