Task 12: Perform User Acceptance Testing
Performing user acceptance testing is comparable to performing Task 9: Perform Functional Testing. In fact, you might choose to execute your test plan or a subset of the plan in this simulated Production environment.
The main difference between these two tasks is that for user acceptance testing, you must arrange for the people who actually use your Waveset application to test it with realistic data.
Though it might be difficult to schedule user participation with people distributed across your organization, user acceptance testing is usually quite valuable. Giving users an advanced look at the next version of your Waveset application generally helps maintain productivity and encourages adoption. Conducting user acceptance testing also demonstrates that the deploying organization is proactive and responsive to the needs of the people who are using the application.
User acceptance testing often uncovers problems and clarifies requirements for your Waveset application. The users might also find issues that are specific to aspects of your platform that were not tested in other environments. Although most developers prefer to find problems in earlier phases, finding problems during user acceptance testing is still much better than finding problems after you upgrade the Production environment.
Even if you ultimately decide to go into production with issues or limitations, you will know about these issues or limitations ahead of time. Key users are then prepared to communicate the problems and any workarounds to other users of the application.
To Address Issues Discovered In User Acceptance Testing
As with Task 9, if you have to fix any problems, you must do the following:
- © 2010, Oracle Corporation and/or its affiliates