DCB Test Plan
1. Unit testing
Unit test verifies one piece of code in isolation. For e.g. Lending flow working as a single unit of flow.
Code that is unit-testable is code has little dependencies on other modules,.
The coverage of unit tested code is >=80%
2. Karate tests
Positive and negative flow for:
Lending library – Pickup library flow (3 Roles)
Lending library – Borrowing/Pickup library flow (2 Roles)
Cancellation Flow
3. Integration tests
Integrated test flow between edge-dcb and mod-dcb modules.
4. API (integration) testing
5. Initial DCB configuration for tenant
6. Functional testing scope
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
Lending library – Pickup library flow (3 Roles)
Lending library (request/item/loan statuses and details, circulation log actions). DCB Lending Flow Details
Borrowing library (request/item/loan statuses and details, circulation log actions). DCB Borrowing Flow Details
Pickup library (request/item/loan statuses and details, circulation log actions). DCB Pickup Flow details
Lending library – Borrowing/Pickup library flow (2 Roles)
Lending library (request/item/loan statuses and details, circulation log actions)
Borrowing/Pickup library (request/item/loan statuses and details, circulation log actions). DCB Borrowing_PickUp Flow Details
Cancellation flow
Lending library cancellation
Borrowing library cancellation
Pickup library cancellation
DCB initiated cancellation
FOLIO (ECS)
Lending library – Pickup library flow (3 Roles)
Lending library – Borrowing/Pickup library flow (2 Roles)
Cancellation flow
Validation on existing item barcode, user type (dcb/shadow)
DCB circulation (loan policies/rules, DCB item renewal, circulation log)
7. Regression testing of regular FOLIO circulation