Orders test will consider the following conditions:
- 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
- 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
- INPUT:
- User sets status to "incomplete"
EXPECTED RESULT:
- "Details" window pops up.
- INPUT:
- User presses manual order button AND has security access to that
function
EXPECTED RESULT:
- "Manual Order" window pops up.
- 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
- INPUT:
- User presses auto order button AND has security access to that
function
EXPECTED RESULT:
- "Auto Order" window pops up.
- INPUT:
- User presses details button
EXPECTED RESULT:
- "Details" window pops up.
- INPUT:
EXPECTED RESULT:
- INPUT:
- User presses sort by button
EXPECTED RESULT:
- "Sort By" window pops up.
- INPUT:
- User presses print button AND an order is highlighted
EXPECTED RESULT:
- That order is printed out
- INPUT:
- User presses print button AND no order is highlighted
EXPECTED RESULTS:
- The orders database is printed out
- INPUT:
EXPECTED RESULTS:
- The main menu is displayed.
| | | | | | | | | |
Manual Order: Process 4.1
|
| | | | | | | | | |
Manual Orders will consider the following conditions:
- INPUT:
EXPECTED RESULT:
- FIND dialogue window appears
- INPUT:
EXPECTED RESULT:
- SORT_BY dialogue window appears
- INPUT:
- MOUSE_CLICK on ADD_GROCERY
EXPECTED RESULT (Process 4.1.3):
- Order Details table is updated appropriately
- INPUT:
- MOUSE_CLICK on REMOVE_GROCERY
EXPECTED RESULT (Process 4.1.4):
- Order Details table is updated appropriately
- INPUT:
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.
- INPUT:
EXPECTED RESULT (Process 4.1.5):
- MANUAL ORDERS dialoge window closes, NEW_ORDER is displayed with no changes.
- INPUT:
- MOUSE_CLICK off a valid area
EXPECTED RESULT:
- INPUT:
- MOUSE_CLICK on "UPC" FIELD
EXPECTED RESULT:
- "UPC" FIELD enters "data entry mode"
- "Description" FIELD is cleared
- INPUT:
- MOUSE_CLICK on "Description" FIELD
EXPECTED RESULT:
- "Description" FIELD enters "data entry mode"
- "UPC" FIELD is cleared
- 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
- 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
- INPUT:
- INVALID "UPC"
- MOUSE_CLICK on OK
EXPECTED RESULT:
- error message displays "UPC not found"
- FIND dialogue box is re-displayed
- INPUT:
EXPECTED RESULT:
- FIND dialoge window closes, NEW_ORDER is displayed with no changes.
- INPUT:
- MOUSE_CLICK off a valid area
EXPECTED RESULT:
- INPUT:
- MOUSE_CLICK on "UPC" FLAG
EXPECTED RESULT:
- "UPC" FLAG is set
- "Description" FLAG is cleared
- INPUT:
- MOUSE_CLICK on "Description" FLAG
EXPECTED RESULT:
- "Description" FLAG is set
- "UPC" FLAG is cleared
- 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
- 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
- INPUT:
EXPECTED RESULT:
- SORT BY dialoge window closes, NEW_ORDER is displayed with no changes.
- INPUT:
- User modifies "number received" on table and inputs a positive
integer
EXPECTED RESULT:
- "Orders" and "Groceries Ordered" databases are updated
- 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
- 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
- INPUT:
- User presses "exit" button
EXPECTED RESULT:
- main orders screen is displayed
- 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
- INPUT:
- User presses "ok" button AND one or more criteria are
syntactically incorrect
EXPECTED RESULT:
- Message to user indicating that criteria are syntactically
incorrect
- 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
- 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
- INPUT:
EXPECTED RESULT:
- main orders screen comes up.
- INPUT:
- User presses "ok" with no criteria selected
EXPECTED RESULT:
- Orders list is sorted by order number (decreasing)
- INPUT:
- User presses "ok" with 1 criteria selected
EXPECTED RESULT:
- Orders list is sorted by the criteria selected
- 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
- 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
- INPUT:
- User attempts to select all 4 criteria
EXPECTED RESULT:
- The 4th criteria will not be selected
- INPUT:
- User presses print AND an order is highlighted
EXPECTED RESULT:
- The order information for that order (including detail
information) is printed out
- INPUT:
- User presses print AND no order is highlighted
EXPECTED RESULT:
- All orders in the database are printed out.
- 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
|
| | | | | | | | | |
- INPUT:
- MOUSE_CLICK off a valid area
EXPECTED RESULT:
- INPUT:
- MOUSE_CLICK on "TIME" FIELD
EXPECTED RESULT:
- "Time" FIELD enters "data entry mode"
- INPUT:
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.
- INPUT:
EXPECTED RESULT:
- AUTO-ORDER dialoge window closes, ORDER is displayed with no changes.
- INPUT:
- VALID TIME in "Time" FIELD
- MOUSE_CLICK on APPLY
EXPECTED RESULT:
- Error message displays "Invalid time entered"
- "Time" FIELD enters "data entry mode"
- 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
- INPUT:
EXPECTED RESULT:
|
|
Login
Main Menu
Security
Password
Orders
Product
Personnel
Stores
Cashier
Inventory
Main Page
|