DCB Test Plan

Owned by Irina Pokhylets
Last updated: Dec 11, 2023

1. Unit testing

  1. Unit test verifies one piece of code in isolation. For e.g. Lending flow working as a single unit of flow.
  2. Code that is unit-testable is code has little dependencies on other modules,.
  3. The coverage of unit tested code is >=80%

2. Karate tests

Positive and negative flow for:

  1. Lending library – Pickup library flow (3 Roles)
  2. Lending library – Borrowing/Pickup library flow (2 Roles)
  3. Cancellation Flow 

3. Integration tests

Integrated test flow between edge-dcb and mod-dcb modules.

4. API (integration) testing

    • Request and response validation:
      • manual check of the API endpoints’ functionality
      • missing or invalid parameters during the calls
      • incorrect or unstructured data formats
      • error handling, wrong response codes
    • Authentication and authorization
      • security vulnerabilities of the API key

5. Initial DCB configuration for tenant

    • DCB umbrella instance/ holding
    • DCB loan type
    • DCB cancellation reason
    • DCB service point
    • DCB institution (location)
    • DCB campus (location)
    • DCB library (location)

6. Functional testing scope

  1. UI changes related to displaying DCB (virtual) patrons and items on the following pages (DCB-related UI changes):
    • Loan details
    • Request details
    • Check in
    • Check out
    • Circulation log
    • User details
    • User - Open loans
    • User - Closed loans
  2. Lending library – Pickup library flow (3 Roles)
    1. Lending library (request/item/loan statuses and details, circulation log actions). DCB Lending Flow Details
    2. Borrowing library (request/item/loan statuses and details, circulation log actions). DCB Borrowing Flow Details
    3. Pickup library (request/item/loan statuses and details, circulation log actions). DCB Pickup Flow details
  3. Lending library – Borrowing/Pickup library flow (2 Roles)
    1. Lending library (request/item/loan statuses and details, circulation log actions)
    2. Borrowing/Pickup library (request/item/loan statuses and details, circulation log actions). DCB Borrowing_PickUp Flow Details
  4. Cancellation flow
    1. Lending library cancellation
    2. Borrowing library cancellation
    3. Pickup library cancellation
    4. DCB initiated cancellation
  5. FOLIO (ECS)
    1. Lending library – Pickup library flow (3 Roles)
    2. Lending library – Borrowing/Pickup library flow (2 Roles)
    3. Cancellation flow
    4. Validation on existing item barcode, user type (dcb/shadow)
  6. DCB circulation (loan policies/rules, DCB item renewal, circulation log)

7. Regression testing of regular FOLIO circulation