User Test Plan

ID Name/event Description Expected Result Actual Result

1 Payment Function User will use this function  List down the orders
to make payments, according to the invoice
complete the order. number.
 Counts the total amount to
be paid.
 Counts the amount paid.
 Counts the balance amount.
 Completes the payment.
 Prints the payment receipt.
2 Order Management User will use this function  Displays types of service.
Function to make orders, update  Displays types of clothes.
orders, delete orders, print  Displays and counts the
invoice. weightage of the cloth.
 Make orders.
 Edit order details.
 Delete orders.
 Print invoice.
 Proceeds to payment.
 Doesn’t involve any type of
payment process.
3 Feedback Function User will submit feedback  Displays rating on a scale of
for the laundry service. 1-5.
 Displays text box to type in
invoice number.
 Submits feedback.
 Feedbacks can’t be edited.
 Feedbacks only can be
viewed by manager.
 Feedbacks can’t be submitted
without customer username.
4 Employee Login User will login to the  Validates username and
laundry management password.
system  Allows users to change
password if they forget
password.
 Displays every input as black
dot (•) in the password
textbox.
5 Employee Sign Up User registers new  User records new employee’s
employee and gives them credentials.
access to the system  User creates an account for
new employees to access
certain functions of the
system
6 Report Generator User will use this function  User generates inventory
to generate reports such as report.
sales report, inventory  User generates daily sales
report and feedback report report.
 User generates feedback
report.
 Only manager has access to
view and generate report.
 User can print report.
7 Customer Register User will use this function  User records customer’s
to register new customers credentials.
 User submits customer’s
credentials to the system.
9 Inventory System User will use this function  Displays stock balance
to manage the inventory  Notifies when low stock
and stock balance quantity
 Update the stock balance
Strategies

The strategy we used to carry out the user test plan is Blackbox testing. Blackbox testing
can be defined as a method used to test software functionality without knowing the internal code
structure of the software. (STF, 2019) It can be used on every level of software testing but is mainly
used for higher level acceptation and system - related testing.

There are several techniques to carry out the black box testing. At first, Boundary Value
Analysis (BVA) is the most commonly used black box testing technique, used to find the error in
the input value boundaries rather than the center. Besides that, Equivalence Class Partitioning is
also a technique used to reduce to the number of possible inputs yet effective inputs (Guru 99,
2019). The inputs are divided into classes and each class gets value by using them to test an
application extensively and avoid data redundancy. Moreover, Decision Table Based Testing is
the most robust technique and is ideally applied when the number of combinations of actions is
carried out under different conditions. Furthermore, Requirement Based Testing includes
affirming the software system requirements based on the customer requirements (geeksforgeeks,
2019).

The requirement-based testing method was used to carry out the user testing because the
motive was to satisfy customer’s requirement. Moreover, black box testing strategy also was
chosen because it can be tested by the user itself, as it doesn’t require professional IT knowledge
to carry out. When the user tests the system, they may know the flow and structure of the system
where they can fully use the system which would be useful for the developing team to get
comments and feedbacks from the actual users. Therefore, they can make bug fixes on the
following system maintenance. Moreover, the tester doesn’t have to learn a specific programming
language because the black box testing is only done on the inputs and outputs of the system. At
last, tests can be carried out by an independent body which encourages an objective perspective
and the avoidance of developer - bias.
System Test Plan

ID Name Description Expected Result Actual Result

1 Performance  User logins to the system  Displays list of orders in the
and switches between payment system within 0.5
different pages/forms in seconds after invoice no is
the system which submitted.
requires high memory.  Switching pages should be
smooth.
 System should run up to 15
hours.
 System should do
calculations less than a
second.

2 Accuracy  User registers customers  System should identify

with similar name. customers with similar
 User makes order with names.
the similar item name.  System should identify
similar item names when
making an order or
payment.
3 Reliability  User enters duplicate  Shows error message when
data. duplicate data is entered.
 User enters invalid data.  Shows error message for
 User execute invalid invalid data.
functions.  Shows error message for
invalid action
4 Usability  User checks on the user  System should check if
interface of the entire similar usernames are
system. entered when registering
 User checks if the customers or new
username is unique employees.
 User receives error  System should display error
message when duplicate message when invalid data
data or invalid data is or no data is entered.
entered.
5 Security  User tests the login  Employee’s profile should be
system. secured with password.
 User tests the payment  Manager’s profile should be
system. secured with password.
 Manager and employee only
should access the payment
system.
 System should encrypt and
decrypt password.
Strategy

The non-functional test is the type of testing carried out against non-functional conditions. Most
criteria in functional testing are not considered, so that the availability of a system is checked.
Non-functional requirements are usually those that reflect product quality, especially in the context
of user suitability (TestingWhiz, 2019). The Non-functional Testing parameters are vital elements
when testing is carried out. At first, performance is one of the parameters used to evaluate the
software's performance where the response time is aligned with the desired time (Perforce
Software, Inc, 2019). Moreover, the Security parameter defines how a system is protected from
sudden and deliberate attacks internal and external sources (Guru99, 2019). Besides that, the
accuracy parameter is used to test the accuracy in data input, output and data management.
Furthermore, reliability tests on how software system performs the defined functions continuously
without failing (Guru99, 2019). At last, usability defines the user's ease of learning, operating,
preparing inputs and outputs through system interaction.

There are several advantages of carrying out the non-functional testing. By carrying out
the non-functional testing the system security could be improvised. System security is extremely
important because if a system is not as safe as possible, it is vulnerable to cyber-attacks. Moreover,
performance is a key component of a successful system because the overall efficiency of the
system is greatly improved with a system that does not crash, load times are increased (Chavhan,
2015). This would be an enormous upper hand for major companies like banks. At last, it ensures
the assurance of software quality. The quality assurance of software is important for a high-quality
system, which means that the system is up to a high standard (Pal, 2016). All the above-mentioned
non-functional testing parameters were used to test our system to identify bugs in the system, fix
and enhance the system.