OCUL VDX Testing Checklist by mercy2beans121

VIEWS: 0 PAGES: 3

									                         OCUL VDX Testing Checklist

This checklist has been designed to be used in conjunction with the OCUL Internal Test
Cases spreadsheet. The OCUL Internal Test Cases spreadsheet lists the basic tests
that should be carried out as part of the ‘live’ mode testing process.

This checklist provides further details for the types of checks that should be performed
and the information that should be verified. This checklist will be most helpful when first
beginning to test so that none of the ‘small details’ are overlooked.

Your Role as that of Requester (Borrower):

Basic Request

   ·   Do a search to confirm that the item is not held locally – if it is try to determine
       why VDX may have not found the item (document thoroughly)

   ·   If ZPortal/Z39.50 is used to auto-populate the bib information, did the data come
       into the fields correctly?
           o Did all the data carry over?
           o Was any of the data lost or cut off?
           o Did it appear/populate into the proper fields?
           o Did you get all the data you needed, that will be needed by the responder
               to fill the request?

   ·   Did DocFind generate the rota properly?
          o In select test cases perform a search using the Union Catalogue - did all
             of the locations that have the item appear in the rota (those in Group 1 &
             2)

   ·   Did the authorization status come up correctly?
          o Use the audit table to determine when items came up “Check Manual” –
              report anything unusual

   ·   Did the patron information come in correctly?
          o Note if you used an End User or Staff account when entering the request

   ·   Were you able to send the request?


Responder side

   ·   Did the responder receive the complete information in the request (on screen)
          o Bib information
          o End User information
          o Requester information
          o Message / notes information




                                                                                              1
   ·   Did the responder receive the complete information in the request (printout)
          o Bib information
          o End User information
          o Requester information
          o Message / notes information

Requester side

   ·   Did the responder information come back correctly (on screen)?
          o Due Date
          o Notes
          o Currency
          o Conditions / Reasons

   ·   Did the status update correctly?

   ·   Was the information correctly displayed and included in the reports when you ran
       them?
          o Did all the data carry over?
          o Was any of the data lost or cut off?
          o Did it appear/populate into the proper fields?
          o Did you get all the data you needed, that will be needed by the responder
             to fill the request?


Your Role as that of Responder (Lender):

Requester side

   ·   Were they able to send the request to/via VDX?
   ·   Were they able to receive updated actions from VDX?

Responder side

   ·   Did you receive the complete information in the request in the correct fields?

   ·   Did the reports run? For example, print the Pick list and run batch re-runs.
          o Are all the data fields being populated?
          o Are the fields aligning properly on the page?
          o Are any notes or fields being cut off?

   ·   Were you able to action and send?




                                                                                        2
Reminders

     ·   Take note and/or Record the “Note Type” used when placing the original
         request.

     ·   Make sure that you use a request for the designated material type (loan or
         copy non returnable) as certain actions can not be performed on loans for
         various material types.

     ·   Take note of the User Type used when entering the request.

     ·   As a requester include the test case number and any relevant test history and
         or test goals in the Notes field. Include rota location order information as well
         as directives as the responding location cannot see the rota.
          i.e. Case 7A
               Trent Loc 1 - Answer Non-Supply
               Waterloo Loc 2 – Answer Non-Supply
               Western Loc 3 – Fill request / Ship

     ·   When you manually enter locations in the rota make a note of this on your
         spreadsheet and in the Notes field on the request record. This will be
         important when testing the inclusion of call numbers on the responder’s Pick
         list report.




                                                                     January 23, 2003
                                                      Copyright OCUL VDX Project, TIG




                                                                                        3

								
To top