Presentation is loading. Please wait.

Presentation is loading. Please wait.

 Acceptance testing is a user-run test that demonstrates the application’s ability to meet the original business objectives and system requirements and.

Similar presentations


Presentation on theme: " Acceptance testing is a user-run test that demonstrates the application’s ability to meet the original business objectives and system requirements and."— Presentation transcript:

1

2  Acceptance testing is a user-run test that demonstrates the application’s ability to meet the original business objectives and system requirements and usually consists of a subset of system tests. Source : Wiilliam E. Lewis, Software Testing and Continuous Quality Improvement, 2 nd edition,2005  “… acceptance testing certifies that the software system satisfies the original requirements.” Source : Wiilliam E Lewis, Software Testing and Continuous Quality Improvement, 2 nd edition, 2005  Acceptance testing is defined as that testing, which when completed successfully, will result in the customer accepting the software and giving us their money. Source : Lee Copeland, A Practitioner’s guide to Software Test Design, 2004 Definition COMP8130 V&V - User Acceptance Test (UAT) 2-17

3  We have identified several keywords related to UAT:  final step before rolling out the application,  final stage of testing in application,  fitness purposes,  meet acceptance criteria,  meet the original business objectives and system requirements.  readiness for operational use.  Therefore, we conclude that the User Acceptance Testing is : “ A final testing phase that is conducted during the life cycle of software development, in order to determine whether the developed system meets the agreed requirements and to evaluate the readiness for operational use ”. Definition ( cont..) COMP8130 V&V - User Acceptance Test (UAT) 3-17

4 Testing Types Software Testing and Continuous Quality Improvement, Wiilliam E Lewis COMP8130 V&V - User Acceptance Test (UAT) 4-17

5  It is performed after the software has successfully completed systems testing  A formal UAT is not compulsory, when the end users are satisfied with the other system tests and have been involved continuously throughout the development lifecycle (implicitly conduct acceptance test) The Use of UAT COMP8130 V&V - User Acceptance Test (UAT) 5-17

6 Some steps when doing the UAT :  User Acceptance Test Planning  Designing UAT Test Cases  Review/Approve Acceptance Test Plan  Executing Test Cases  Documenting the defects found during UAT  Resolving the Defects Fixing  Sign Off UAT Activities COMP8130 V&V - User Acceptance Test (UAT) 6-17

7  Test plan - outlines the testing strategy (Acceptance Testing, Entry and Fail Criteria, Test Execution Team, Test Script Developer)  Test cases - guides the team to effectively test the application  Test Log - records all the test cases executed and the actual results  User Sign Off - indicates that the customer are satisfied with the product. UAT Deliverables COMP8130 V&V - User Acceptance Test (UAT) 7-17

8  Structured testing: Conducted based on the test plan and test procedures. It consists various tests against agreed requirements.  Unstructured testing: A test that is conducted by not referring to the test plan It is a free form test which tests the software with the idea of breaking it. UAT Methodologies COMP8130 V&V - User Acceptance Test (UAT) 8-17

9  Advantages written statements of expected behaviour provides repeatability cost effective technique to deliver a high quality of product a risk mitigation strategy  Disadvantages testing coverage limitation requires more efforts and expense during the preparation testing executions Structured Testing COMP8130 V&V - User Acceptance Test (UAT) 9-17

10  Advantages Flexibility in detecting system anomalies it does not require much effort on the preparation phase of testing  Disadvantages In general,errors could not be reproduced difficult to measure the success criteria of the testing activity test coverage is unknown Unstructured Testing COMP8130 V&V - User Acceptance Test (UAT) 10-17

11  Team Leader  Test Analyst  User Representative  Testers  Test Observers COMP8130 V&V - User Acceptance Test (UAT) UAT Team Members

12  Insufficient number of testers  Inexperienced user representative  Incompetent Testers Issues of UAT Management COMP8130 V&V - User Acceptance Test (UAT) 12-17

13  Ideal User acceptance Tester Background Has the experience of user operations and in the use of IT facilities, independent thinker Skills good communicator, need to expect system to fail Independence not involved in the IT project and also in the user specifications, need to be a self-starter. Attitude need to be an optimistic thinker, neutral, need to be analytical. Availability Fully dedicated in doing the Tests Types of User Acceptance Tester COMP8130 V&V - User Acceptance Test (UAT) 13-17

14  Typical User Acceptance Tester Background Involved in the IT project and also in the user specifications Skills Non technical and technical persons Attitude Pragmatic Availability Testing is not the main job Types of User Acceptance Tester ( Cont..) COMP8130 V&V - User Acceptance Test (UAT) 14-17

15 Reasons why it is not possible to find Ideal User acceptance tester  Lack of Software Project Management Knowledge  Not always possible to have independent User Acceptance testers  Generally, testing is not their main job  Too busy with operational activities COMP8130 V&V - User Acceptance Test (UAT) 15-17

16  Teamwork is essential  We are not good at finding errors in our own work  A successful test is one that finds errors  Define testing criteria when defining business requirements  Detachment - during development testers can “look but not touch” (review only)  Not everyone does testing well  It’s almost never right at the first time Rules of Thumb for UAT COMP8130 V&V - User Acceptance Test (UAT) 16-17

17  The user acceptance test as the last testing phase process is important to evaluate the software deliverable against the users’ requirements.  When customers have already involved in development activities and implicitly implementing acceptance test, UAT is not a compulsory step to accomplish. However if we conduct UAT, this will take satisfaction in product deliverable for both of user and vendor  There are several phases in conducting user acceptance test activities, such as planning, designing test cases, forming a testing team, executing test cases, documenting defects, resolving the issues, and signing off the test.  Moreover, UAT can be conducted either in structured or unstructured ways.  For several reasons, it is not possible to have ideal User Acceptance tester Summary COMP8130 V&V - User Acceptance Test (UAT) 17-17

18 Thank You


Download ppt " Acceptance testing is a user-run test that demonstrates the application’s ability to meet the original business objectives and system requirements and."

Similar presentations


Ads by Google