Why I should do UAT (User Acceptance Testing) ?

UAT is the client view (end-user), so the most important tests will be here. I know that you can be a developer that started in QA automation area and you probably don’t like to do these tests and you don’t see the value of them, but as a professional of QA you should be concerned with the client point of view and his expectations with the quality of the product. Remember QA is the area of the quality and it is not only about a pattern and it is about testing as a client.

Reduce chances of error in LIVE Environment: Some scenarios you only discover in the phase UAT. Maximum possible scenarios are identified and tested before software moved to LIVE environment.

Increase User Satisfaction: You can test usability and real performance only in this type of test, because here you can test according with the device, real environment, etc. UAT provides full-fledge access of software to user, which gives him a lot of confidence as well as satisfaction to allow him to test the software that soon he will be using in a LIVE environment.

Reduce risk of regulatory & other compliance: You want to be sure that any mistakes even the most simple not will be forgotten. Some scenarios are discovered only in this phase (Don’t forget that you are working with humans, so if you want to have absolutely sure that nothing was forgotten, it is better test). As in UAT, the system is tested on maximum business scenarios; the risk of regulatory and other compliances that may bring penalties in term of financial impact, opportunity loss or customer dissatisfaction can be minimized.

Reduce Time: You can reduce the time of the teste in this phase, because you will have more knowledge to know if some scenarios are duplicated or not. In new/automated system, there is a chance that the system has automated some business processes along with some changes in existing processes, which might have increased some process steps found to be unnecessary or wasting time in the LIVE environment, UAT allows users to identify those unnecessary steps before going into the LIVE environment, it allows organizations to save time by reducing process steps that may take time in the LIVE environment and incur extra costs.

Business reputation: Quality is reputation, if your client discover a small bug in your application, the client confiability will fall together with the quality of your product. For this reason the client point of view is the most important test. If due to software solution, organization is unable to provide the services to its customer or provide the services with delay or somehow impact customer by giving wrong figures or showing wrong transaction in customer’s account, this may blow the business reputation and definitely results in customer dissatisfaction, and with this, the company may lose a good amount of business that was successfully in hand having the legacy system in place.

Bye guys 🙂

Sources:

http://www.batimes.com/articles/uat-tips-and-templates.html
https://www.develop.com/training-course/user-acceptance-testing-for-business-analysts

Definition of User Acceptance Testing (UAT)

UAT directly involves the intended users of the software. UAT can be implemented by making software available for a free beta trial on the Internet or through an in-house testing team comprised of actual software users.

Following are the steps involved in in-house UAT:

  • Planning: The UAT strategy is outlined during the planning step.
  • Designing test cases: Test cases are designed to cover all the functional scenarios of the software in real-world usage. They are designed in a simple language and manner to make the test process easier for the testers.
  • Selection of testing team: The testing team is comprised of real world end-users.
  • Executing test cases and documenting: The testing team executes the designed test cases. Sometimes it also executes some relevant random tests. All bugs are logged in a testing document with relevant comments.
  • Bug fixing: Responding to the bugs found by the testing team, the software development team makes final adjustments to the code to make the software bug-free.
  • Sign-off: When all bugs have been fixed, the testing team indicates acceptance of the software application. This shows that the application meets user requirements and is ready to be rolled out in the market.

UAT is important because it helps demonstrate that required business functions are operating in a manner suited to real-world circumstances and usage.

 

Fonts: http://www.techopedia.com/definition/3887/user-acceptance-testing-uat