- C Language
- CSS
- MainFrame
- VBScript
- PHP
- XML
- C++ Tutorials
- Ajax
- JavaScript
- CSS3
- UML
- jQuery
- Microsoft AJAX
Tutorials TestingThis article attempts to explain the process of User Acceptance Testing.
Once the application is ready to be released the crucial step is User Acceptance Testing.
In this step a group representing a cross section of end users tests the application.
The user acceptance testing is done using real world scenarios and perceptions relevant to the end users.
Sponsored Links
User Acceptance Testing is often the final step before rolling out the application.
Usually the end users who will be using the applications test the application before ‘accepting’ the application.
This type of testing gives the end users the confidence that the application being delivered to them meets their requirements.
This testing also helps nail bugs related to usability of the application.
Before the User Acceptance testing can be done the application is fully developed.
Various levels of testing (Unit, Integration and System) are already completed before User Acceptance Testing is done. As various levels of testing have been completed most of the technical bugs have already been fixed before UAT.
To ensure an effective User Acceptance Testing Test cases are created.
These Test cases can be created using various use cases identified during the Requirements definition stage.
The Test cases ensure proper coverage of all the scenarios during testing.
During this type of testing the specific focus is the exact real world usage of the application. The Testing is done in an environment that simulates the production environment.
The Test cases are written using real world scenarios for the application
The user acceptance testing is usually a black box type of testing. In other words, the focus is on the functionality and the usability of the application rather than the technical aspects. It is generally assumed that the application would have already undergone Unit, Integration and System Level Testing.
However, it is useful if the User acceptance Testing is carried out in an environment that closely resembles the real world or production environment.
The steps taken for User Acceptance Testing typically involve one or more of the following:
.......1) User Acceptance Test (UAT) Planning
.......2) Designing UA Test Cases
.......3) Selecting a Team that would execute the (UAT) Test Cases
.......4) Executing Test Cases
.......5) Documenting the Defects found during UAT
.......6) Resolving the issues/Bug Fixing
.......7) Sign Off
User Acceptance Test (UAT) Planning:
As always the Planning Process is the most important of all the steps. This affects the effectiveness of the Testing Process. The Planning process outlines the User Acceptance Testing Strategy. It also describes the key focus areas, entry and exit criteria.
Designing UA Test Cases:
The User Acceptance Test Cases help the Test Execution Team to test the application thoroughly. This also helps ensure that the UA Testing provides sufficient coverage of all the scenarios.
The Use Cases created during the Requirements definition phase may be used as inputs for creating Test Cases. The inputs from Business Analysts and Subject Matter Experts are also used for creating.
Each User Acceptance Test Case describes in a simple language the precise steps to be taken to test something.
The Business Analysts and the Project Team review the User Acceptance Test Cases.
Selecting a Team that would execute the (UAT) Test Cases:
Selecting a Team that would execute the UAT Test Cases is an important step.
The UAT Team is generally a good representation of the real world end users.
The Team thus comprises of the actual end users who will be using the application.
Executing Test Cases:
The Testing Team executes the Test Cases and may additional perform random Tests relevant to them
Documenting the Defects found during UAT:
The Team logs their comments and any defects or issues found during testing.
Resolving the issues/Bug Fixing:
The issues/defects found during Testing are discussed with the Project Team, Subject Matter Experts and Business Analysts. The issues are resolved as per the mutual consensus and to the satisfaction of the end users.
Sign Off:
Upon successful completion of the User Acceptance Testing and resolution of the issues the team generally indicates the acceptance of the application. This step is important in commercial software sales. Once the User “Accept” the Software delivered they indicate that the software meets their requirements.
The users now confident of the software solution delivered and the vendor can be paid for the same.
Sponsored Links
In the Traditional Software Development Lifecycle successful completion of User Acceptance Testing is a significant milestone.
The Key Deliverables typically of User Acceptance Testing Phase are:
1) The Test Plan- This outlines the Testing Strategy
2) The UAT Test cases – The Test cases help the team to effectively test the application
3) The Test Log – This is a log of all the test cases executed and the actual results.
4) User Sign Off – This indicates that the customer finds the product delivered to their satisfaction
In this article we studied the process of ‘User Acceptance Testing’.
| The information provided is really good. thanks for all the people who has taken interest in collecting the above information. |
|
Hi Frnds, I am working in Back end testing can any body send me winrunner Documents. thanks, Venkatanarayana reddy |
|
Thnak you very much, I am new in Testing field actually in IT field. Right now I have been working as PeopleSoft UAT Tester. I have to write test case as well as test them. I ma wondering do I have to write internal functionality of that particular PeopleSoft functionality as well in that test case. Anybody can give me idea about this please..... |
| This is really a very useful tutorial since i am new to testing.It gives a clear picture of testing process. |
|
Nice It gives me a lot of familiarity in UAT since I am new in Testing. Thanks I would share it to my batchmates |
|
hi there, i am working in a testing team. can u please send me a doccument containing a powerful concept about levels of testing. |
|
Hi, can u any body tell me that how to do the user acceptance testing in that what is the actual process. Because some company's having saperate UAT testing team is there. That's why the functional testing people dont know how to do the UAT testing in real time. In any comp is having no resources of the saperate UAT testing team that time the functional testers come into the picture. That's why can u any body tell me not only me this is very useful for others also Thank you Have a nice day |
| hai..i am new to this field..this tutorial is really an helpful one.....thank you/............. |
| Hi all, I am new to UAT how can we gurantee that the web application is good for users can anybody explain? I have created some scenarios for testing but that seem to be all functional tests , so what exactly and how to prove that the application is user friendly and all that . |
| Give more details to understand the concept clearly. |
| It will be really helpful if someone gives a difference between functional and UAT supproted with approriate examples.what are the points thta should be consider while writing the test case for functional testing and UAT |
| I am new to testing field.This information helped me a lot |
| The material is so clear that I could understand the concept very well |
|
Its great to study this concept but it is lacking some where, I am working as QA LEAD and having 9 yrs exp.... I want to suggest one thing like add more people who involved and some sample test cases as the freshers who come in testing can learn more.. |
|
Hi Frnds, i am working in product based company so can u please send me a doccument for UAT activities for any applications (Banking or Financial) |
|
This is a good article... To add to this i would say that the UAT test cases should be detailed and simple but should encourage the user to find the features on his own, instead of spoon feading the user with the exact steps of carrying out the test. This will bring out the usability issues. Also the point on using the requirements document to come out with use cases is a very important step. But analysing how each feature would be used in the field is not easy to do. |
| I want to learn UAT so this article is very useful for me. Thank you. |
|
Hello, I am working towards IT field aspecially in testing. This UAT material is really really good. Thanks |
|
This is really a very good understanding about UAT. Actually in your tezt plan document, you always use propar format and its start from Introduction, Scope (a) In Scope (b)Out scope, Impacted system, System Overview, Risk / Issues, UAT strategy, Schedule (Scenario / scripts). Thanks, |
|
I am totally new about testing. This article helps me lot to understand the whole idea of UAT... I would like to have some practical example & more information regarding Testing tools like Win Runner, Mercury Test Director.... can you please send me details on pinkmilan@gmail.com |
| This material is very helpful for testers.thanks |
| This is really helpfull for us |
| This material is the best of all material that i have seen for UAT. It helps a lot to me. |
| Very good material for the testers |
| it is very good one ... it have a lot of good information that i need it as SQA |
|
Can UAT be done before functional testing, if not what why not |
| Hi Valiant, Normally UAT is done after all the Unit,Integration and System level are completed. This the stage where simply you are asking yourself or the testing team (or incase of Agile model testing a representation is also given from the client side), if the software or system meets the scope of the Requirement that was agreed upon. |
|
The objective of software development is to develop the software that meets the true needs of the user, not just the system specifications. To accomplish this, testers should work with the users early in a project to clearly define the criteria that would make the software acceptable in meeting the user needs. As much as possible, once the acceptance criterion has been established, they should integrate those criteria into all aspects of development. This same process can be used by software testers when users are unavailable for test; when diverse users use the same software; and for beta testing software. Although acceptance testing is a customer and user responsibility, testers normally help develop an acceptance test plan, include that plan in the system test plan to avoid test duplication; and, in many cases, perform or assist in performing the acceptance test. nglmartin |
|
Hi All, UAT is very similar to what we do in IT Hardware projects in Transitions and Process...... Very much Interesting concept and useful in any business organisation... |
| when exactly the UAT test cases are prepared. |
| In case if we find a major bug in UAT how to solve the bug? I mean is there any way to find the solution in a easy way |
|
Great effort...kudos However see if you can add little more info viz., 1. what is the entrance criteria 2. what is the exit criteria 3. what should you do when a bug is detected during the UAT process?( why is it different from a bug found during the normal test cycle) 4. how do u track a bug during UAT phase 5. what do u mean by UAT test strategy...what does it contain 6. how different are these UAT test cases vis-a-vis normal test cases 7. who decides on sign-off 8. what is the role of testing team and dev team during UAT pahse 9. where possible try and use samples... I know that, hypothetically a tester should be aware of all these things..but then if it is documented, will probably help hundreds of new comers have a far more clear understanding of the subject. |
|
Hi Kumar, UAT test case preparation start from BRD review and finished after solution review. |
|
Hi Srilatha, If we find major/Critical bug in UAT then those defects need to fixed prior to release.Business will determine risk and business impact. If it is critical to business function then we need to resolve it. other wise business will defer to future release. Hope this help. |
|
This material has put in simple and un-ambiguous words a UAT. But between when the 1st cycle of the UAT is concluded and the resolution of the bugs found, what is the state of the UAT? Is it still "on-going"? or do the users sign off with the condition that there would be a retest when the issues are fixed? Thank you. |
| plz anyone can tell me some of the best prctices related to UAT... |
