Cornette Library Acceptance Testing

April 1997 screenshot [1]


Acceptance testing is completed after the system is installed and before it is released to the end user. The system must pass predefined benchmarks that are specified before testing begins. If the tests fail to meet the requirements of the end users, further refinement will be necessary. The final part of the UAT can also include a parallel run to compare the new system against the current one [4]. The beta testing phase would be considered part of this process.


April 1999 screenshot [2]


Benchmarks of system performance, communication, access, backup, logging, indexing, management, and monitoring could have been included in the most recent revision of the Cornette Library. Looking back at its’ design from 1997, that might not have been the case. But it is clear that the recent designers have improved upon some of these tests. Faculty and graduate students might have been involved in this process to ensure end users would be capable of using the new website and its’ added functionalities. UAT usually involve one or more of the following: [5]
1. User Acceptance 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

Use cases could have been used when implementing the Cornette Library website. It seems plausible that the site designer did not include tips and hints to locate the resources that a typical user may find helpful. Mock users may have found it difficult and time consuming when interfacing in certain zones. That scenario might have been addressed and corrected with the addition of extra areas of explanation when attempting to use the resource locators. Subjective user satisfaction might have been a requirement with the latest revisions. It is clear that earlier versions were not as appealing as is the latest design. Government regulations and standards would have also played a role in their tests. Accessibility for disabled individuals were of a concern.


April 2004 screenshot [3]


The goal of acceptance testing is similar to that of preventive maintenance: to identify and prevent potential unscheduled failure of the system while in service [6]. UAT will also help in minimizing future costs of maintaining the system.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License