Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • Each feature or peace of functionality 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, both standard ECS and ECS + mod-tlr

  • 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

Ramsons features UAT

Workflows/tasks to test

UXPROD-4559 ECS w/mod-tlr (borrowing vs Central?)

  • Create request in borrowing tenant

  • Edit request in borrowing tenant

  • Duplicate request in borrowing tenant

  • Check item out from Central tenant

  • Check item in to Central tenant

  • Find above transactions in the Circ log & verify info in each column

  • TLR enablement

    • Central/data

    • Consortium

  • Look at Loan details

  • Look at User details

  • Print pick slips

  • Print hold search slips - item

  • Print hold search slips - title

 UXPROD-4657 Mediated requests

  • Create a new m-request

  • Edit a m-request

  • Approve folio created m-request

  • Decline folio created m-request

  • Decline locate created request

  • Edit locate created request

  • Duplicate folio created m-request

  • Duplicate locate created m-request

  • Use search to find m-request

  • Use filters to find m-request

UXPROD-4119 Secure requests (Congressional loans)

  • Place secure request in Congressional tenant and ensure patron data is anonymous in the Central tenant

  • Reorder a request queue in the Congressional tenant and ensure the queue in the Central tenant aligns with your changes and the same in the Central tenant to Congressional tenant

  • Cancel a request in the Central tenant and ensure the private mediated request has changed to the appropriate status (Closed - Cancelled?) and the same for the Congressional tenant request (Closed - Cancelled)

  • Edit a private request in both tenants and ensure the changes are reflected in the other tenant

Check a private request out and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant

  • Check that the patron information in Item details, Loan details are obfuscated (Action ellipses)

  • Check a private request in and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant