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

 


Unit Tests                                   

 

Objective                                   
     To ensure that:
     
  1. user can enter data into the Cancel a Book page,
  2. syntactically incorrect inputs are detected,
  3. given Call Number and/or User ID exist in database, and
  4. correct message on the status of the cancel-a-hold request is displayed.

 

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 "Cancel request is successful" or a "Patron doesn't have this book on hold" message is 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):
Successful request. To test this, enter a call number of a book which is currently on hold by this patron.
Customer ID: 10072
Call Number: 1111107890

Expected Results - A "Request to cancel a book on hold is successful" message is displayed.

Unsuccessful request. To test this, enter a call number of a book which is not currently on hold by this patron.
Customer ID: 10072
Call Number: 2211107890

Expected Results - A "Patron doesn't this book on hold" message is displayed.

 


Integration Tests                                   

 

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

 

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

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

To check 2):
Test all buttons (SEARCH, LIST,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 (Putting A Book On Hold) Canceling A Book On Hold Next (Paying A Fine)

Copyright ©1997 VoidWorks Software Inc.

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