Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Version:
1.0
Date: 15th August, 2008
Revision History
Date
15th August, 2008
Version
1.0
Description
First version
Author
Test Team
Version:
1.0
Date: 15th August, 2008
BACKGROUND
The Library Management System is an online application for assisting a librarian in managing a book
library in a University. The system would provide basic set of features to add/update clients, add/update
books, search for books, and manage check-in / checkout processes. The test team will test the system
based on the requirement g.
INTRODUCTION
This test plan is a basic guideline for future testing in the LMS. It mainly focuses on two problems: what
we will test and how we will test.
TEST ITEMS
3.1
GUI test
3.2
3.3
Database test
3.4
Network test
FEATURES TO BE TESTED
4.1
GUI test
System should provide a GUI for librarians to interface with the backend library database
4.2
Database test
4.2.1
4.2.2
4.3
4.3.1
Add a student
4.3.2
Update/delete student
4.3.3
Add a book
4.3.4
Update/delete book
4.3.5
4.3.6
Check-in book
4.3.7
Check-out book
4.3.8
4.3.9
Network test
Version:
1.0
Date: 15th August, 2008
5.1
Licensing requirement
Reason: Since they are free software, they need not be tested.
APPROACH
6.1
6.2
6.3
Validation testing
7.1
GUI test
Pass criteria: librarians could use this GUI to interface with the backend library database without any
difficulties
7.2
Database test
Pass criteria: Results of all basic and advanced operations are normal (refer to section 4)
7.3
7.3.1
Add a student
Pass criteria:
Each customer/student should have following attributes: Student ID/SSN (unique), Name, Address
and Phone number.
The retrieved customer information by viewing customer detail should contain the four attributes.
7.3.2
Update/delete student
Pass criteria:
Updates can be made on full. Items only: Name, Address, Phone number
The updated values would be reflected if the same customer's ID/SSN is called for.
7.3.3
Add a book
Pass criteria:
Each book shall have following attributes: Call Number, ISBN, Title, Author name.
The retrieved book information should contain the four attributes.
7.3.4
Update/delete book
Pass criteria:
Version:
1.0
Date: 15th August, 2008
The data items which can be updated are: ISBN, Title, Author name
The updated values would be reflected if the same call number is called for
7.3.5
Pass criteria:
The product shall let Librarian query books detail information by their ISBN number or Author or
Title.
The search results would produce a list of books, which match the search parameters with following
Details: Call numtber, ISBN number, Title, Author
The display would also provide the number of copies which is available for issue
The display shall provide a means to select one or more rows to a user-list
A detailed view of each book should provide information about check-in/check out status, with the
borrowers information.
The search display will be restricted to 20 results per page and there would be means to navigate from
sets of search results.
The user can perform multiple searches before finally selecting a set of books for check in or
checkout. These should be stored across searches.
A book may have more than one copy. But every copy with the same ISBN number should have same
detail information.
The borrowers list should agree with the data in students account
7.3.6
Check-in book
Pass criteria:
The check-in can be initiated from a previous search operation where user has selected a set of books.
The return date would automatically reflect the current system date.
Any late fees would be computed as difference between due date and return date at rate of 10 cents a
day.
A book, which has been checked in once, should not be checked in again
7.3.7
Check-out book
Pass criteria:
The checkout can be initiated from a previous search operation where user has selected a set of books.
Version:
1.0
Date: 15th August, 2008
The issue date would automatically reflect the current system date.
The due date would automatically be stamped as 5 days from current date.
A book, which has been checked out once, should not be checked out again
A student who has books due should not be allowed to check out any books
The max. No of books that can be issued to a customer would be 10. The system should not allow
checkout of books beyond this limit.
7.3.8
Pass criteria:
This view would display details about a selected book from search operation
The details to be displayed are: Call number, IBN, Title, Author, Issue status (In library or checked
out), If book is checked out it would display, User ID & Name, Checkout date, Due date
7.3.9
Pass criteria:
7.4
Network test
Pass criteria: Results of operations (ping, ftp and ODBC connectivity check) are normal
TEST DELIVERABLES
8.1
Test plan
8.2
Test report
ENVIRONMENTAL NEEDS
9.1
9.2
10 RESPONSIBILITIES
10.1 Mr. XYZ and Mr. ABC are involved in test plan document
Version:
1.0
Date: 15th August, 2008
11 STAFFING
Mr. XYZ, leader of testing group
Mr. IOP, member of testing group
Mr. LOP, member of testing group
12 SCHEDULE
12.1 Test plan is due on April 4
12.2 Test report is due on May 7
13 RESOURCES
13.1 Developers of the system are involved in testing process (debugging, unit testing, even integrity
testing)
13.2 Users of the system are involved in testing process (integrity testing)
14 RISKS CONTINGENCIE
Should prototype of the system not be due before April 23, test report could not be guaranteed to be
available on May 7
15 APPROVALS