Restaurant Automation System

TEST SUITE DESIGN AND TEST RESULTS

Group – 13

Submitted By:-
Himanshu Verma (13CS30015)
Prateek Jhunjhunwala(13CS10035)

1|Page
TABLE OF CONTENTS

1. Introduction…….………………………………………….……………………………………………………5
1.1 Description………………………………………………………………………………………5
1.2 Related Documents…………..…………………………………………………………….5
1.3 Hardware Requirements……….………………………………………………………..5
1.4 Software Requirements…………………………………………………………………..6
2. Validation and Verification…………………………………………………………………………6
2.1 Manager………………………………………………………………………………………6
2.1.1 Log In Validation………………………………………………………………6
2.1.2 Manager Home screen……………………………………………………7
2.1.3 View Sale’s Receipt………………………………………………………….8
2.1.4 Detailed Sales Receipt……………………………………………………..9
2.1.5 Sales Statistics Pie Chart………………………………………………….10
2.1.6 View Expense Data…………………………………………………………..12
2.1.7 Detailed Expense Data……………………………………………………..13
2.1.8 Sales Statistics Bar Chart…………………………………………………..14
2.1.9 View/Print Menu……………………………………………………………….16
2.1.10 Update Menu…………………………………………………………………19
2.1.10.1 Add Item……………………………………………………………20
2.1.10.2 Delete Item……………………………………………………….22
2.1.10.3 Modify Price………………………………………………….....24
2.2 Sales Clerk…………………………………………………………………………………….26
2.2.1 Login Validation……………………………………………………………….26
2.2.2 Sales Clerk Home screen……………………………………………………27
2.2.3 Sell Item…………………………………………………………………………..28
2.2.3.1 Input Validation…………………………………………………28
2.2.3.2 Delete Item from Bill……………………………………………31
2.2.3.3 Print Bill……………………………………………………………….33
2.2.4 Enter Purchase………………………………………………………………….33
2.2.4.1 Add Ingredient Validation……………………………………34
2.2.4.2 Delete Ingredient...……………………………………………..38
2.2.4.3 Confirm Order……………………………………………………..40

2|Page
 2.2.5 Issue Ingredient……………………………………………………………….41
2.2.5.1 Quantity Validation……………………………………………..41

3. Test Plan……………………………………………………………………………………………………43
3.1 Manager and Clerk Login……………………………………………………………………43
3.2 Manager……………………………………………………………………………………………….43
3.2.1 Update Menu………………………………………………………………………………43
3.2.1.1 Add Item to Menu…………………………………………………………43
3.2.1.2 Delete Item…………………………………………………………………..44
3.2.1.3 Change Price……………………………………………………………………44
3.2.2 View Sales Receipt……………………………………………………………………….45
3.2.3 View Detailed Sales Receipt………………………………………………………….45
3.2.4 View Expense Data……………………………………………………………………….45
3.2.5 View Detailed Expense Data………………………………………………………..46
3.2.6 Sales Pie Chart……………………………………………………………………………46
3.2.7 Sales Bar Chart…………………………………………………………………………….46
3.3 Clerk…………………………………………………………………………………………………….47
3.3.1 Sell Item……………………………………………………………………………………..47
3.3.2 Issue Ingredient………………………………………………………………………….47
3.3.3 Enter Purchase……………………………………………………………………………48
4. Chapter Summary…………………………………………………………………………………….49

3|Page
4|Page
 1. Introduction

This document is a high-level overview defining testing strategy

for the Restaurant Automation System (RAS).

1.1 Description
System testing was important to a project, testing is to validate the
system whether meet the requirement of the system. Software testing is used
to test the functionality of each application. Software testing enables to
investigate the quality of the system. Software testing able to verify whether
does the system meets the business and technical requirements has been request
in the objective. Software testing can be also stated as a process to validate
and verify the software programs. The software testing is being carried out by
using a testing methodology.

1.2 Related Documents

1.2.1 LIS SRS
1.2.2 LIS SA-SD
1.2.3 LIS UML diagrams

5|Page
1.3 Hardware requirements
The software has been tested on machine with a minimum of the following
specifications:
RAM: preferably over 1GB
Processor: 64 bit

1.4 Software Requirements

The LIS has the following software dependencies:
Operating System: Any Windows or Linux based operating System
SQL Client: MySQL

6|Page
2.Validation and Verification

2.1 Manager

2.1.1 Login Validation

This is the login validation for the front-end system. The system will

validate the Username and Password key in by the manager. Unauthorized

user is not allow to the login into the system either Username or password

is incorrect.

7|Page
 2.1.2 Manager’s Home Screen

This is the manger’s Home Screen which appears when manager entered the
correct login username and password. This window contains the various function
which manager can do.

8|Page
 2.1.3 View Sales Receipt

This is the window for viewing Sales Receipts. This window can be open only by
Manager. In this window we select the range of date for which we want to see
the sales receipts (only the total sale of that day). After clicking the display
button all the sales receipts from the selected range displayed in the window.

9|Page
 2.1.4 Detailed Sales Receipt

This window is for the detailed sales receipt. In this window we just select the
range of data for which we want to see the sales receipts in detail. Detailed
Sales receipts means per item’s quantity sold and their price in selected date
range. Average price is the cost of an item for a quantity.

10 | P a g e
 2.1.5 Sales Statistics pie chart

11 | P a g e
 After clicking on the “Sales Statistics Pie chart” button in the Manager’s home
Screen, a window appears in which we have to select the date range for which
we want to see the pie chart. After selecting the date range a window is prompt
out having a pie chart which shows how much quantity of each item sold in that
particular range of date. Pie chart also contains percentage sale of each item.

12 | P a g e
 2.1.6 View Expense Data

This is the window for viewing Sales Expense Data. This window can be open
only by Manager. Sales Expenses Data means the total ingredient purchased by
the restaurant for making the food. In this window we select the range of date
for which we want to see the Sales Expenses (only the total expenses of that
day). After clicking the display button all the expenses from the selected range
displayed in the window.

13 | P a g e
 2.1.7 Detailed Expense Data

This window is for the detailed expenses data. In this window we just select the
range of data for which we want to see the expense in detail. Detailed
Expenses data means per ingredient purchased quantity and their price in
selected date range. Average price is the cost of an ingredient for a quantity.

14 | P a g e
 2.1.8 Sales Statistics Bar chart

15 | P a g e
 After clicking on the “Sales Statistics Bar chart” button in the Manager’s home
Screen, a window appears in which we have to select the date range for which
we want to see the bar chart. After selecting the date range a window is
prompt out having a bar chart which shows how much quantity of each item sold
in that particular range of date. Pie chart also contains percentage sale of each
item.

16 | P a g e
 2.1.9 View/Print Menu

This window is open when manager clicked on the View/Print menu option. This
window displays all the items which are present in the restaurant with their
price.

17 | P a g e
18 | P a g e
 After clicking on Print Menu button in view/menu window, a new window is
prompt out which contains all the necessary regarding print. After clicking the
print button in the new window, bill will be printed.

19 | P a g e
 2.1.10 Update Menu

2.1.10.1 Add Item

This window will prompt out when manager click on the “Add Item to Menu” button
in the Modify Menu window. Now, manager can fill the details of the item he wants
to add in the menu.

20 | P a g e
After filling all the details in the “Add menu” window, a confirmation message is
displayed which ensure that the item is added successfully in the menu.

21 | P a g e
2.1.10.2 Delete Item

This window will prompt out when manager click on the “Add Item to Menu” button
in the Modify Menu window. Now, manager can choose the item from the combo box
which he wants to delete.

22 | P a g e
This message is displayed when the manager selected the item from the combo box
which he wants to delete. This message ensures that the item is deleted from the
menu card.

23 | P a g e
2.1.10.3 Modify Price Validation

24 | P a g e
25 | P a g e
 2.2 Sales Clerk

2.2.1 Login Validation

This is the login validation for the front-end system. The system will validate
the Username and Password key in by the Sales Clerk. Unauthorized user is not
allow to the login into the system either Username or password is incorrect.

Here the Sales-Clerk provides the correct username and password.

26 | P a g e
2.2.2 Sales-Clerk Home Screen

This is the Sales-Clerk’s Home Screen which appears when Sales-Clerk entered
the correct login username and password. This window shows the various
function which Sales-Clerk can do.

27 | P a g e
 2.2.3 Sell Item

2.2.3.1 Input Validation

28 | P a g e
29 | P a g e
30 | P a g e
2.2.3.2 Delete the Selected Item from bill

31 | P a g e
32 | P a g e
2.2.3.3 Print Bill Confirmation

33 | P a g e
2.2.4 Enter Purchase

2.2.4.1 Add Ingredient Validation

34 | P a g e
35 | P a g e
36 | P a g e
37 | P a g e
2.2.4.2 Delete Selected Row

38 | P a g e
39 | P a g e
2.2.4.3 Confirm Order

40 | P a g e
2.2.5 Issue Ingredients

2.2.5.1 Quantity Validation

41 | P a g e
42 | P a g e
3. Test Plan

3.1 Manager and Clerk Login Page:

No. Test Domain Test Expected Actual Conclusion
Data Output Output
1. Validate user input : Leave An error An error Successful
empty field text box message message
blank display display
2. Validate user input : Enter An error An error Successful
password not match different message message
password display display
3. Validate user input: Enter Login and Same as Successful
Enter correct details correct redirect to expected
username respective
and pages
password

3.2 Manager
3.2.1 Update Menu:
3.2.1.1 Add an item to the menu:
No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid input Valid price and Item to be Item added Successful
quantity entered added and a
message
displayed
2. Invalid Input Enter negative An error An error Successful
price or quantity message message
display display
3. Invalid input Empty any of the An error Error Successful
required four message message is
fields display displayed

43 | P a g e
 3.2.1.2 Delete an Item from the menu:
No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid input Select an item from Item is Same as Successful
the menu using deleted expected
combo box from
menu and
a message
is
displayed

3.2.1.3 Change price of an item:

No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid input Select an item from Menu is Same as Successful
the menu using updated expected
combo box and and price
enter a price>0 is
changed,
message is
displayed

2. Invalid Input Negative price is Error Same as Successful

entered for the message is expected
menu item displayed

44 | P a g e
3.2.2 View Sales Receipt
No. Test Domain Test Data Expected Actual Conclusion
Output Outpu
t
1. Valid Input Enter the range of Sales is Same as Successful
dates using calendar displayed expected
(date wise)
2. Invalid Input One or more of the Error Same as Successful
dates is not selected message expected
displayed

3.2.3 View Detailed Sales Receipt

No. Test Domain Test Data Expected Actual Conclusion
Output Outpu
t
1. Valid Input Enter the range of Sales per Same as Successful
dates using calendar item is expected
displayed
for the
range of
dates
2. Invalid Input One or more of the Error Same as Successful
dates is not selected message expected
displayed

3.2.4. View Expense Data

No. Test Domain Test Data Expected Actual Conclusion
Output Outpu
t
1. Valid Input Enter the range of Expense id Same as Successful
dates using calendar displayed expected
(date wise)
2. Invalid Input One or more of the Error Same as Successful
dates is not selected message expected
displayed

45 | P a g e
 3.2.5. View Detailed Expense Data:
No. Test Domain Test Data Expected Actual Conclusion
Output Outpu
t
1. Valid Input Enter the range of Expense Same as Successful
dates using calendar per item is expected
displayed
for the
range of
dates
2. Invalid Input One or more of the Error Same as Successful
dates is not selected message expected
displayed

3.2.6. Sales Pie Chart

No. Test Domain Test Data Expected Act Conclusion
Output ual
Ou
1. Valid Input Enter the range of Pie Chart is Same as Successful
tpu
dates using calendar displayed expected
t
showing
percentage of
each item in
total revenue
2. Invalid Input One or more of the Error message Same as Successful
dates is not selected displayed expected

3.2.7. Sales Bar Chart

No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid Input Enter the range of Bar Chart is Same as Successful
dates using calendar displayed expected
showing sales
of each item
in the menu
for the range
of date
2. Invalid Input One or more of the Error message Same as Successful
dates is not selected displayed expected

46 | P a g e
3.3 For Clerk:

3.3.1. Sell Item:

No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid Input Correct item code Item is added Same as Successful
and quantity is to the bill expected
entered
2. Invalid Input Invalid item code Error message Same as Successful
entered or negative displayed expected
quantity is entered

3.3.2. Issue Ingredient:

No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid Input Item is selected form Ingredient is Same as Successful
the combo box and issued and expected
correct quantity is the same is
entered subtracted
from the
inventory. If
the level of
ingredient
falls below
threshold
level, alert
message is
displayed
2. Invalid Input Entered quantity is Error Same as Successful
greater than available message expected
quantity or less than displayed
0

47 | P a g e
 3.3.3. Enter Purchase:
No. Test Domain Test Data Expected Actual Conclusion
Output Output
1. Valid Input New item is added Ingredient is Same as Successful
to the list, correct added to the expected
item price and table
quantity is entered
and item name is
not empty
2. Valid Input Item is selected Ingredient is Same as Successful
from the list and added tot able expected
correct price and
quantity is entered

3. Invalid Input Quantity or price Error message Same as Successful

entered is less than is displayed expected
0

48 | P a g e
5.1 Chapter Summary

A well design system should able to provide an error free and well

function for the user. If a system has well tested then the system

may produce understandable output, not always terminate during run-

time. Through the software testing, every modules and fields in the

system had been tested carefully, otherwise the adequate message

box will present to the user for each input. Though the message box

or message display, the user can understand what the action is require

to be taken by following the instruction of the system.

49 | P a g e