SquidSoft Inc. - GUIDOs
Detailed Design Document - Testing Plan


           Process 4: Orders           

Orders test will consider the following conditions:

  1. INPUT:
    • User clicks on status field and changes status AND user has security access to do this
    EXPECTED RESULT:
    • The order is updated in the orders database

  2. INPUT:
    • User clicks on status field and changes status AND DOES NOT have security access to do this
    EXPECTED RESULT:
    • Message informing user that he/she does not have access to update orders

  3. INPUT:
    • User sets status to "incomplete"
    EXPECTED RESULT:
    • "Details" window pops up.

  4. INPUT:
    • User presses manual order button AND has security access to that function
    EXPECTED RESULT:
    • "Manual Order" window pops up.

  5. INPUT:
    • User presses manual order button AND DOES NOT have security access to that function
    EXPECTED RESULT:
    • Message informing user that he/she does not have access to the manual orders function

  6. INPUT:
    • User presses auto order button AND has security access to that function
    EXPECTED RESULT:
    • "Auto Order" window pops up.

  7. INPUT:
    • User presses details button
    EXPECTED RESULT:
    • "Details" window pops up.

  8. INPUT:
    • User presses find button
    EXPECTED RESULT:
    • "Find" window pops up.

  9. INPUT:
    • User presses sort by button
    EXPECTED RESULT:
    • "Sort By" window pops up.

  10. INPUT:
    • User presses print button AND an order is highlighted
    EXPECTED RESULT:
    • That order is printed out

  11. INPUT:
    • User presses print button AND no order is highlighted
    EXPECTED RESULTS:
    • The orders database is printed out

  12. INPUT:
    • User presses exit button
    EXPECTED RESULTS:
    • The main menu is displayed.

           Manual Order: Process 4.1           

Manual Orders will consider the following conditions:

  1. INPUT:
    • MOUSE_CLICK on FIND
    EXPECTED RESULT:
    • FIND dialogue window appears

  2. INPUT:
    • MOUSE_CLICK on SORT_BY
    EXPECTED RESULT:
    • SORT_BY dialogue window appears

  3. INPUT:
    • MOUSE_CLICK on ADD_GROCERY
    EXPECTED RESULT (Process 4.1.3):
    • Order Details table is updated appropriately

  4. INPUT:
    • MOUSE_CLICK on REMOVE_GROCERY
    EXPECTED RESULT (Process 4.1.4):
    • Order Details table is updated appropriately

  5. INPUT:
    • MOUSE_CLICK on SUBMIT
    EXPECTED RESULT (Process 4.1.2):
    • A new instance of Order is created in the database
    • A new instance of Grocery Ordered is created in the database for each different item on Order Details table
    • The Manual Orders window closes and the screen returns to the Order screen.

  6. INPUT:
    • MOUSE_CLICK on CANCEL
    EXPECTED RESULT (Process 4.1.5):
    • MANUAL ORDERS dialoge window closes, NEW_ORDER is displayed with no changes.

           Find: Process 4.1.1           

  1. INPUT:
    • MOUSE_CLICK off a valid area
    EXPECTED RESULT:
    • no change occurs

  2. INPUT:
    • MOUSE_CLICK on "UPC" FIELD
    EXPECTED RESULT:
    • "UPC" FIELD enters "data entry mode"
    • "Description" FIELD is cleared

  3. INPUT:
    • MOUSE_CLICK on "Description" FIELD
    EXPECTED RESULT:
    • "Description" FIELD enters "data entry mode"
    • "UPC" FIELD is cleared

  4. INPUT:
    • VALID "UPC"
    • MOUSE_CLICK on OK
    EXPECTED RESULT:
    • FIND dialogue window closes, left table of NEW_ORDER displays grocery indicated by UPC as highlighted

  5. INPUT:
    • VALID "Description"
    • MOUSE_CLICK on OK
    EXPECTED RESULT:
    • FIND dialogue window closes, left table of NEW_ORDER displays highlighted grocery with description most closely matching the one indicated by Description

  6. INPUT:
    • INVALID "UPC"
    • MOUSE_CLICK on OK
    EXPECTED RESULT:
    • error message displays "UPC not found"
    • FIND dialogue box is re-displayed

  7. INPUT:
    • MOUSE_CLICK on CANCEL
    EXPECTED RESULT:
    • FIND dialoge window closes, NEW_ORDER is displayed with no changes.

           Sort by: Process 4.1.2           

  1. INPUT:
    • MOUSE_CLICK off a valid area
    EXPECTED RESULT:
    • no change occurs

  2. INPUT:
    • MOUSE_CLICK on "UPC" FLAG
    EXPECTED RESULT:
    • "UPC" FLAG is set
    • "Description" FLAG is cleared

  3. INPUT:
    • MOUSE_CLICK on "Description" FLAG
    EXPECTED RESULT:
    • "Description" FLAG is set
    • "UPC" FLAG is cleared

  4. INPUT:
    • "UPC" FLAG is SET
    • MOUSE_CLICK on OK
    EXPECTED RESULT:
    • SORT BY dialogue window closes, left table of NEW_ORDER displays groceries sorted in order of UPC

  5. INPUT:
    • VALID "Description"
    • MOUSE_CLICK on OK
    EXPECTED RESULT:
    • SORT BY dialogue window closes, left table of NEW_ORDER displays groceries sorted in alphabetical order of description

  6. INPUT:
    • MOUSE_CLICK on CANCEL
    EXPECTED RESULT:
    • SORT BY dialoge window closes, NEW_ORDER is displayed with no changes.

           Detaile: Process 4.3           

  1. INPUT:
    • User modifies "number received" on table and inputs a positive integer
    EXPECTED RESULT:
    • "Orders" and "Groceries Ordered" databases are updated

  2. INPUT:
    • User modifies "number received" on table and inputs a negative integer
    EXPECTED RESULT:
    • Message to user indicating that number received must be a positive integer

  3. INPUT:
    • User modifies "number received" on table and inputs non integers
    EXPECTED RESULT:
    • Message to user indicating that number received must be a positive integer

  4. INPUT:
    • User presses "exit" button
    EXPECTED RESULT:
    • main orders screen is displayed

           Find Orders: Process 4.4           

  1. INPUT:
    • User presses "ok" button AND all search criteria are blank
    EXPECTED RESULT:
    • Message to user indicating that at least one criteria must be given

  2. INPUT:
    • User presses "ok" button AND one or more criteria are syntactically incorrect
    EXPECTED RESULT:
    • Message to user indicating that criteria are syntactically incorrect

  3. INPUT:
    • User presses "ok" button AND criteria are syntactically correct AND a match(s) is found
    EXPECTED RESULT:
    • A list of orders matching the criteria is returned

  4. INPUT:
    • User presses "ok" button AND criteria are syntactically correct AND no matches are found
    EXPECTED RESULT:
    • message to user indicating that no matches were found

  5. INPUT:
    • User presses exit button
    EXPECTED RESULT:
    • main orders screen comes up.

           Sort by: Process 4.5           

  1. INPUT:
    • User presses "ok" with no criteria selected
    EXPECTED RESULT:
    • Orders list is sorted by order number (decreasing)

  2. INPUT:
    • User presses "ok" with 1 criteria selected
    EXPECTED RESULT:
    • Orders list is sorted by the criteria selected

  3. INPUT:
    • User presses "ok" with 2 criteria selected
    EXPECTED RESULT:
    • Orders list is sorted by the primary criteria selected and then by the secondary criteria selected

  4. INPUT:
    • User presses "ok" with 3 criteria selected
    EXPECTED RESULT:
    • Orders list is sorted by the primary criteria selected then by the secondary criteria selected then by the tertiary criteria selected

  5. INPUT:
    • User attempts to select all 4 criteria
    EXPECTED RESULT:
    • The 4th criteria will not be selected

           Print: Process 4.6           

  1. INPUT:
    • User presses print AND an order is highlighted
    EXPECTED RESULT:
    • The order information for that order (including detail information) is printed out

  2. INPUT:
    • User presses print AND no order is highlighted
    EXPECTED RESULT:
    • All orders in the database are printed out.

  3. INPUT:
    • User presses print AND printer is not responding
    EXPECTED RESULT:
    • Message to user indicating that printer is not responding

           Automatic Ordering: Process 4.7           

  1. INPUT:
    • MOUSE_CLICK off a valid area
    EXPECTED RESULT:
    • no change occurs

  2. INPUT:
    • MOUSE_CLICK on "TIME" FIELD
    EXPECTED RESULT:
    • "Time" FIELD enters "data entry mode"

  3. INPUT:
    • MOUSE_CLICK on ORDER NOW
    EXPECTED RESULT:
    • Search of Inventory database results in the creation of a single Order, with an instance of Groceries Ordered created for each item found to be under-stocked.

  4. INPUT:
    • MOUSE_CLICK on CANCEL
    EXPECTED RESULT:
    • AUTO-ORDER dialoge window closes, ORDER is displayed with no changes.

  5. INPUT:
    • VALID TIME in "Time" FIELD
    • MOUSE_CLICK on APPLY
    EXPECTED RESULT:
    • Error message displays "Invalid time entered"
    • "Time" FIELD enters "data entry mode"

  6. INPUT:
    • INVALID TIME in "Time" FIELD
    • MOUSE_CLICK on APPLY
    EXPECTED RESULT:
    • TIME is set
    • dialoge window closes, NEW_ORDER is displayed with no changes

           Exit: Process 4.8           

  1. INPUT:
    • User presses exit button
    EXPECTED RESULT:
    • Main menu is displayed
Login  
Main Menu  
Security  
Password  
Orders  
Product  
Personnel  
Stores  
Cashier  
Inventory  

Main Page  


About SquidSoft Inc. This site created and maintained
with Mortar