TESTING AND QUALITY ASSURANCE (QA) IN LIBRARY SOFTWARE: STRATEGIES FOR RELIABLE RELEASES
TL;DR
QA needs to ensure not just the quality of the software, but also the integrity of the data, data schema migration, and backward compatibility, to ensure the quality of the software release.
Abstract
Library software is at the crossroads of complex domain knowledge, diverse data, and varying user needs. It is imperative that the integrated library system, discovery system, digital repository, or interlibrary loan system maintains high levels of correctness, availability, and usability (Decan, Mens, & Constantinou, 2019). Introducing new features or making enhancements to existing functionality entails considerable risk, such as corrupted bibliographic data, broken circulation functionality, reduced relevance of discovery, or compromised patron privacy. Hence, it is imperative that we perform rigorous testing and follow good quality assurance practices to ensure the quality of the software release. Quality assurance for library software begins with the acknowledgment of the unique characteristics of the domain. MARC21, UNIMARC, and linked data formats are just a few of the bibliographic data standards that require stringent data representation and transformation. Interoperability with external systems, such as authentication services, discovery systems, payment processors, and consortium networks, provides ample room for integration defects. Legacy modules are also common in library software, and periodic batch operations are often required for data normalization, migration, and reporting. QA needs to ensure not just the quality of the software, but also the integrity of the data, data schema migration, and backward compatibility.