Here in this posted the template for UAT for mobile application hope this will be help full for preparing UAT
Stage: Acceptance
User Acceptance Test (UAT) Plan
Application Name
Document Version: [1.0]
Date: [dd/mm/yy]
Contents
1Document Management
1.1Contributors
Please provide details of all contributors to this document.
Role | Department | Name |
Owner | ||
Contributor | <Business Partner> | |
Contributor | <Business Partner> | |
Contributor | <Business Partner> |
1.2Version Control
Date | Version | Author | Section | Amendment |
12/11/2011 | V 1.0 | All | Initial Draft | |
2USER ACCEPTANCE TESTING
2.1User Acceptance Definition
2.2UAT Responsibilities
Role | Name | Responsibilities |
Project Manager | Communication with Customer to agree format and scope of UAT | |
Agree acceptance criteria with the Customer prior to commencing UAT | ||
Business Analyst | Assist Customer with the creation of a detailed test plan | |
Test Co-ordinator (Business) | Ensure that a detailed test plan is available for test users | |
Ensure that bugs identified during UAT are logged in the MIS Test Log | ||
Ensure testing takes place within agreed timeframes |
3UAT STRATEGY
The User Acceptance Test Plan should be used to record the Customer’s sign off of the documented scenarios. It is recommended that detailed test plans be used to record the results of user testing.
The document is a high level guide, and is not intended as a replacement for any specific user acceptance testing procedures that individual areas might have.
Consideration |
Date Agreed |
Details |
Test Approach |
|
|
Assumptions & Constraints |
|
|
Setup of Test Environment |
|
|
Test Scenarios |
|
|
Test Period |
|
|
4USER TESTING
User testing should be based on the pre agreed test scenarios or acceptance criteria. It should be noted if the scenarios have been sourced from the BRD, or if they have been identified subsequently.
Identified in BRD | ||
Scenario | Date Tested | Notes |
Identified Post BRD | ||
Scenario | Date Tested | Notes |
Any issues identified during UAT should be added to the MIS Test Log. It may be agreed that UAT can be signed off while some issues remain – please add the test log reference to the appropriate section above if this is the case.
5UAT RESULTS
5.1Open Issues
Please insert a copy of any open issues from the Test Log, together with details of why these issues remain open at the sign off of the Acceptance Stage.
5.2Document Sign Off
Business Project Manager | Name |
Project Manager | Name |
This template will more useful for creating mobile application UAT Doc.