Software Testing-User Acceptance Testing
3)Follow - Up
-
It isn’t sufficient just to find an error; the tester must also record the conditions prior to starting a test, the actions taken during the test, and what results occurred.
- The tester must produce physical evidence, for example screen prints, and be able to repeat the problem.
- If testing problems are not reciprocated, will only be able to record the problem for historical purposes in the event it is reproduced in the future.
- Test results of User Acceptance Testing will reflect certain items requiring change in specifications or functionality.
- These items will be raised as change requests to be registered in the change control process.
- To ensure adequate control on the clearance of errors and to improve management forecasting of UAT completion, each incident must be recorded separately by the tester using the Acceptance Test Feedback Form..
Reporting
- As well as logging problems that result from the discovery of defects, testers will also encounter test incidents caused by the need for clarification, or the need for enhancements. Ambiguities in specifications are common and may not be discovered until UAT. These are clarified and resolved, between the teams involved, and agreed to be either a software defect, to be cleared now, a clarification to be applied to the specifications, or an enhancement to be provided in some future release.
- Detailed checklists will be prepared for testing. These checklists shall list each parameter, which the artifact is being tested toward. Checklists shall be prepared by the UAT team prior to commencement of these tests.
- All user acceptance testing and feedback shall be captured on the Review or Test Activity Record (Appendix B). However, user acceptance testing will be done against detailed test cases prepared by the UAT team prior to commencement of this phase.
- Once all the feedback has been resolved, the fine-tuned application / artifact shall be released again to the UAT team for additional testing.
- The development team clears errors, and provides a new release, incorporating changes and enhancements of the software to the UAT team. This process is repeated until all reported incidents are resolved to the UAT organization’s satisfaction.
4)Re -Testing
The application / artifact released to the UAT team for retesting shall be tested again for the points submitted in the feedback sheets. Detailed regression testing shall occur as per the Integration / Regression Test Plan to be produced for the integration test phase.
OUTPUT
The following will form the outputs of the testing activities and will be stored electronically in the "Test Results" folder secured in an archive.
a) Verified and approved test case records
b) Test results captured on test activity records
c) Screen dumps of error screens
d)Updated checklists
User Acceptance test feedback form
