Library Management Sample Test Plan

Prepared by: Ms / Mr. ……………
Prepared Date: …/…/…

Introduction -:
The Library Management System application for assisting a librarian in managing library books. The system would provide basic set of features to add/update clients, add/update books, search for books, dues if any and manage check-in / checkout processes. This test plan is a basic guideline for future testing in the LMS.

Scope -:
The system would provide basic set of features to add/update members, add/update books, dues if any and manage check in specifications for the systems based on the client’s statement of need.

Environment Requirement -:
Hardware -: Three Dual Core or above machines needed
Software -: Microsoft Windows XP installed

Testing Strategies -:
1. Unit Testing :
Definition : Test smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation.
Participants/ Tested by : Developers
Methodology : Used for the Database test, records in each table, Basic function test, add a student, add a book, Network test

2. System and Integration Testing -:
Definition : Integration testing is the phase in software testing in which individual software modules are combined and tested as a group.
System integration testing (SIT) is a high-level software testing process in which testers verify that all related systems maintain data integrity and can operate in coordination with other systems in the same environment.
Participants/ Tested by : System Tester
Methodology : It is used for the Database test, Queries for insert, update, delete the records

3. Performance and Stress Testing -:
Definition : Determine how a system performs in terms of responsiveness and stability under a particular workload.
Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it
Participants/ Tested by : Tester
Methodology : It is used for the Database test, records in each table, Basic function test, Network test

4.User Acceptance Testing -:
Definition : Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies Participants/ Tested by : Users / End Users
Methodology : It is used for Whole System Test

5. Automated Regression Testing -:
Definition : Uncover new errors, or regressions, in existing functionality after changes have been made to a system, such as functional enhancements, patches or configuration changes.
Participants/ Tested by : Tester
Methodology : It is used for Whole System Test

Test Schedule -: