Document Navigator For The Design Index (Testing Document)
Previous Section
(Customer Administration) 		This Section
(Transactions)		 Next Section
(Entity Relationship Diagram)
Previous (Renewing A Book) Putting A Book On Hold Next (Canceling A Book On Hold)

 

Unit Tests                                   

 

Objective                                   
     To ensure that:
     
  1. user can enter data into the Hold a Book page,
  2. syntactically incorrect inputs are detected,
  3. given Call Number and/or User ID exist in database, and
  4. the status of the request to hold this book. The request may be unsuccessful due to:
    - the book is being on hold
    - the customer has too many books outstanding (including those on hold)

 

Data Used                                   
     
To test 1):
Type inputs into the two text entry fields in the Hold a Book page.
Customer ID: 1007
Call Number: 1111107890

Expected Results - The two fields will allow entry of data.

To check 2):

 

Condition(s) Input To Test
Customer ID
a) no input
b) non-numeric 22$245
c) valid 10072
Call Number
a) no input
b) non-numeric 11111abcd1
c) valid 1111107890

Expected Results - a & b) The error window is displayed stating that the input for Customer ID / Call Number is invalid.
c) Either a "Hold request is successful" message will be displayed or a "Hold is unsucessful" (message due to the description in test 4) will be displayed.

To check 3):
Try different valid input pairs knowing that one (or both) of them does not exist in the database.
Customer ID: 555551
Call Number: 9876543210

Expected Results - The error window is displayed stating that the Customer ID does not exist in the database.

To check 4):
There are two cases to be tested:

The book has been put on hold. One way to do this test is to put a book, say the one whose call number is 1234567890, and then try to place a hold on that book again.

Expected Results - A "Hold is unsuccessful: the book is currently on hold" message will be displayed.

The customer has too many books outstanding. To test this, keep signing out books on one particular User ID until the books outstanding reach maximum limit. Then try to place a book on hold using this User ID.

Expected Results - A "Hold is unsuccessful: The patron's outstanding books has reached maximun limit" message will be displayed.

 

Integration Tests                                   

 

Objective                                   
     To ensure that:
     
  1. Hold A Book page can be accessed, and
  2. all buttons (SEARCH, OK, CANCEL, CLEAR, HELPx, PRINT) on window operate as expected.

 

Data Used                                   
     
To check 1):
Press "Hold A Book" button on Transaction Administration page.

Expected Results - The Hold a Book page will be displayed.

To check 2):
Test all buttons (SEARCH, OK, CANCEL, CLEAR, HELP, PRINT) one at a time.

Expected Results - Information (or functions) pertaining to the selected button will be displayed (or carried out).

 

Document Navigator For The Design Index (Testing Document)
Previous Section
(Customer Administration) 		This Section
(Transactions)		 Next Section
(Entity Relationship Diagram)
Previous (Renewing A Book) Putting A Book On Hold Next (Canceling A Book On Hold)
Copyright ©1997 VoidWorks Software Inc.

Send mail to the Group Leader or the Webmaster
Pages created and maintained with Mortar