Acceptance testing is basically done by the user or customer. After the system test has corrected all or most defects, the system will be delivered to the user or customer for acceptance testing.
The goal of acceptance testing is to establish confidence in the system. Acceptance testing is the final phase of testing before moving the software application to Market or Production environment. The main purpose of this testing is to validate the end to end business flow. It does NOT focus on the cosmetic errors, Spelling mistakes or System testing. This testing is carried out in separate testing environment
The main purpose of this testing is to validate the end to end business flow. It does NOT focus on the cosmetic errors, Spelling mistakes or System testing. This testing is carried out in the separate testing environment.
Prerequisites of User Acceptance Testing
Prior to starting the UAT following checkpoints to be considered:
- The Business Requirements should be available.
- The development of software application should be completed & different levels of testing like Unit Testing, Integration Testing & System Testing is completed.
- All High Severity, High Priority defects should be verified. No, any Showstoppers defects in the system.
- Check if all reported defects should be verified prior to UAT starts.
- Check if Traceability matrix for all testing should be completed.
- Before UAT starts error like cosmetic error are acceptable but should be reported.
- After fixing all the defects regression Testing should be carried out to check fixing of defect not breaking the other working area.
- The separate UAT environment similar to production should be ready to start UAT.
- The Sign off should be given by System testing team which says that Software application ready for UAT execution.
When to perform UAT :
This is typically the last step before the product goes live or before the delivery of the product is accepted. UAT is the product itself is thoroughly tested.
Types of UAT
Alpha Testing : Alpha testing performed to identify all possible issues/bugs before releasing the product to everyday users or public. The focus of this testing is to simulate real users by using black box and white box techniques. The aim is to carry out the tasks that a typical user might perform. Alpha testing is carried out in a lab environment and usually, the testers are internal employees of the organization.
Beta Testing : Beta testing takes place at customer’s site. It sends the system to users who install it and use it under real-world working conditions. The goal of beta testing is to place your application in the hands of real users outside of your own engineering team to discover any flaws or issues from the user’s perspective that you would not want to have in your final, released version of the application.
What to Test in User Acceptance Testing?
- Based on the Requirements definition stage use cases the Test cases are created.
- Also, the Test cases are created considering the real world scenarios for the application.
- The actual testing is to be carried out in environments that copy of the production environment. So in the type of testing is concentrating on the exact real world use of the application.
- Test cases are designed such that all area of application is covered during testing to ensure that an effective User Acceptance Testing.