A Brief Guide for Creating a User Acceptance Test

Gabriel Knight By Gabriel Knight, 9th Aug 2011 | Follow this author | RSS Feed | Short URL http://nut.bz/2z0fhh5f/
Posted in Wikinut>Guides>Technology>Computer Software

A guide leading the reader from the Requirements Definition Phase to the sign-off Phase of user acceptance testing.

Introduction

User Acceptance Testing, or UAT, is performed after the creation of the application. Unit, integration and system testing has been performed before reaching UAT. User acceptance testing allows the running of the application to verify the developers met all the requirements. User acceptance testing finds bugs needing to be addressed concerning usability issues.

Requirements Definition Phase

During the Requirements Definitions phase of the project a list of requirements are outlined. There will also be a list of possible add-ons. The add-ons are not requirements but more of a wish list. If the developers have time to add them then the client will be happy. However, in many cases the wish list items will be added into the application at a later date. The first thing to do is read this requirements list. These requirements are what “need” to be tested.

User Acceptance Strategy

Create a User Acceptance Strategy. Using the defined requirements determine what kind of team you will need. You will need to know how many people you will need and what kind of knowledge they will bring to the table. This strategy will also have test cases, execution of test cases, bug tracking, resolution of bugs and a Sign Off stage.

UAT Test Cases

Create UAT Test Cases. These test cases are designed around the requirements and will involve input from the Business Analysis team, Project Management team and Developer team. The test cases are viewed from a user-friendly point of view. Try to break the application as a user would. The key here is to not follow the directions of the development team. They will send directions on how everything is supposed to work. The user will be lost and do things they are not supposed to, you can bet on it. This is the thing you are trying to test for. When the user users the application incorrectly, what will break and how bad.

The testing is strictly black-box testing. All white-box testing should have been performed before this stage.

Examples of UAT test cases are as follows:

Test that calculations are performed correctly.
Items are saved correctly and in the right format.
Numerical Fields do not accept non-numbered entries (letters, asterisk, etc.).
Look for misspellings throughout.

Test cases should be prepared for each window that appears. So, the test case for looking for misspellings should appear on each test case for each window. Not stated once at the beginning of the project.

UAT Testing

Begin the user acceptance testing.

Select any other members of the team that should be added. It is best to get people that have not worked on the application. They will have new eyes and will not know how the application ‘should’ work.

Perform the user acceptance testing. The team will follow the test cases and try to 'break' the application.

Record any defects or bugs found during the execution phase. The user acceptance testing team will record any and all bugs found by them.

Developers will now fix the bugs found by the user acceptance team. If bugs are found that are not defined in the User Acceptance Strategy then the development team may choose not to fix them. If this occurs let your testing manager know. If they think it is a bug that needs to be fixed they can contact project management. From there the client will be called to find out what they want to do. If the bug falls into the scope of the requirements then the bug will be fixed. If it does not then program management and the client will come to an agreement. It will wither not be fixed, fixed for free or an added fee will be charged to fix the bug.

Once all requirements are met then you will enter the Sign Off stage. At this point you tell the client that everything is ready to start production. The client will sign off stating they are happy with your work and you will send all test cases, strategies and procedures to the client. Upon receiving all materials and code the client will pull you in full.

Links

My Other Computer Links at Wikinut:

Five Best Compression Tools

Other Work at Wikinut:
Five Types of Lingerie-Baby Dolls to Teddys

Tags

Black Box, Requirements, Sign Off, Software, Strategy, Test Case, Testing, Uat, User Acceptance Test

Meet the author

author avatar Gabriel Knight
Freelance writer for US, UK, and Australia. Looking for more clients. SEO, web pages, articles, etc.

Share this page

moderator johnnydod moderated this page.
If you have any complaints about this content, please let us know

Comments

Add a comment
Username
Can't login?
Password