Arun,
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 u2018acceptingu2019 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
UAT is primarily done by the users though the consultants are available for helpin them out.
SIT- System Integration Testing: Final integration testing is accomplished through the execution of predefined business flows, or scenarios, that emulate how the system will run your business. These business flows, using migrated data from the pre-existing systems, will be performed in a multifaceted computing environment comprised of SAP, third-party software, system interfaces and various hardware and software components. It is this environment that builds the necessary level of confidence that the solution is complete and will perform in your business.
Final integration tests need to be an evolutionary process that is driven from your previous testing efforts. The test cases and scenarios that were used for Baseline and Final Configuration need to be reviewed and enhanced for the integrated test. These selected cases can be combined to represent a business process flow such as a revenue cycle or a material acquisition cycle. Problems encountered during these efforts also need to be tested under an integrated environment. Final Integration test cannot be viewed as an independent, but as a capstone effort that brings together and builds upon all previous testing efforts.
Final Integration testing focuses on cross-functional integration points, as well as end-to-end business processes. A well defined Final Integration test plan starts with the testing of the cross-functional integration points (touch points) and ends with the end-to-end testing of critical business processes identified within the Business Blueprint.
Hope this helps you. Let me know if you need anyother information.
Rgds
Manish
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.