Each feature that team Vega completes should have at least one user acceptance testing (UAT) session
UAT is needed for functional feature work in single tenant and ECS environments
UAT should occur as soon as possible to enable the identification of bugs and issues as early as possible
Both types of environments need:
to be snapshot-like, but with persistent data
to include all circulation modules (Check in, Check out, Circulation log, Requests, fees and fines, patron notices, loans, etc.), plus Inventory, Users, and Settings
to have applicable permissions for the above and specific to the features being tested
to be accessible to community testers and members
an appropriate data set and configuration for the feature/case being tested
for example, multiple (25-30) instance, holding and item records with valid (scannable?) barcodes
multiple patron records
General
Content
Integrations