System testing is a critical phase in the development of library and information management systems, ensuring that the entire system functions as intended before deployment. For professionals managing digital catalogues, automated circulation, or integrated library systems in Kenya, rigorous system testing guarantees reliability, accuracy, and user satisfaction. This chapter explores the various types of system testing tailored to library environments and highlights the significance of detecting and resolving system faults through debugging.

5.0 Types of system testing

System testing checks the complete, integrated library system against its requirements before it goes into service. A library system is made of modules such as user registration, lending and returns, the catalogue search and stock control, and each can pass its own checks and still fail when the modules work together. Different types of testing look at the system from different angles, so a library team plans several of them rather than relying on one.

Software testing

Software testing checks the library software as a whole product against the system requirements written during analysis. The tester works through the main tasks a librarian or member performs, for example registering a member, issuing a book, renewing a loan and calculating an overdue fine, and compares what the system does with what the requirements say it should do. Any difference is recorded as a defect and sent back to the developer.

Unit testing

Unit testing checks the smallest parts of the software one at a time, such as the routine that calculates a due date or the form that validates a membership number. Each unit is tested alone with chosen inputs, including wrong ones, so that a fault is found in the unit itself and not hidden behind other modules. Unit tests are usually written and run by the developer before the units are put together.

Integration testing

Integration testing checks that tested units work correctly when they are joined. In a library system, for example, the lending module must pass the right information to the fines module and to the catalogue, so that a returned book shows as available and any fine appears on the member's account. Integration faults are often faults in the data passed between modules, not in the modules themselves.

Usability testing

Usability testing checks how easily the intended users can learn and use the system. Real users, such as a librarian at the circulation desk and a student searching the catalogue, are asked to complete set tasks while the tester notes where they hesitate, make mistakes or need help. The findings show where screens, menus, messages and instructions should be made clearer.

Other types of system testing

Functional testing checks each function against its specification, performance testing checks response time and stability when many users search at once, security testing checks that only authorised staff can change records and that member data is protected, and compatibility testing checks that the system displays and works on the devices, browsers and operating systems its users have. These are planned alongside the four types above.

5.0.1 Importance of system testing

Ensuring system reliability

Testing confirms that the system behaves consistently under different conditions. For example, the availability status of a book must update correctly when several loans are issued at the same time, without errors.

Detecting defects early

Faults found before the system goes live cost less and take less time to correct. A fault in the membership renewal process found during testing, for instance, is corrected before any member is affected.

Enhancing user satisfaction

A system that has been tested thoroughly gives users a smooth experience and encourages them to adopt it. Services such as online reservation of study space or renewal of loans are used more when they work first time.

Maintaining data integrity

Testing shows that data entered into the system stays accurate and consistent when it is saved, searched, changed and reported. This matters because library records are the evidence of what the library holds and who has borrowed it.

Supporting system maintenance

Documented test cases and results give a baseline for later maintenance and upgrades. When the library adds a new feature or corrects a fault, the same tests can be repeated to confirm that nothing that worked before has stopped working.

Chapter Summary

This chapter explored the various types of system testing, emphasizing their roles in verifying different aspects of a system's functionality and performance. The importance of system testing was highlighted, showing how it ensures the system meets user requirements and operates reliably under expected conditions. System debugging was examined as a critical process for identifying and resolving errors discovered during testing to improve overall system quality. The chapter also covered performing system settings, which involves configuring the system environment to support accurate and efficient testing activities. Finally, the development of a comprehensive system testing report was discussed, detailing how to document testing outcomes, issues found, and recommendations for further action to support informed decision-making and system improvement.