ITE 2312 – IT Quality Assurance 2020S2

SQA Case Study

Submitted by:
I.J.Wijesooriya(E1941044)
Bachelor of Information Technology (External Degree)
Faculty of Information Technology
University of Moratuwa
1) Identify five risks you can see in above mention case study.

 Updates - Adding Customer details to the system

A new functionality is going to be added in future.

Other impacts:
One of the most common risks of online stores is of identity theft. Criminals get hold
of customer personal information and then use the information. There are various
ways to steal the identity.
Phishing – normally takes place by emails. These emails seem to be sent by the bank
or an online store and ask for the personal details to rectify some order.

 Search functionality
Searching items on the store with different names.

 Payment functionality
It is the act of testing the base functionality of the payment. It is to verify whether the
application behaves in the same way as it is supposed to be like handling orders,
calculation, an addition of VAT as per the country etc.

 Basic Usability - Customers using different digital devices

It involves basic usability testing of the system. It checks whether a user can freely
navigate through the screens without any difficulties.

 Delivering the products on time

By considering the geographical location and current pandemic situation the
products may not be able to deliver on time.
2) How could you mitigate the identified problems? Identify and suggest 5
main functional testing types with justification.

 Adding Customer details

SMOKE TESTING
This is performed on the newly build given by the developers to QA team to verify
if the basic functionalities are working or not. This is going to be the first test done
on any new build. The objective is not to perform exhaustive testing, but to verify
that the critical functionality of the system is working fine. If the smoking testing
fails then the build is rejected and forwarded to the development team to fix the bugs
and create a new build.

A new section is design to the customer details as per mentioned in the case study. It
may consists of features like updating the information by the users (customer),
visibility functionality and etc. The testing should be done for all the functionalities.

 Search functionality

INTEGRATION TESTING
This performed to test individual components to check how it functions together.
This performed to test the modules which are working fine individually and do not
show bugs when integrated.

The complete search function works when developers build the following modules.
1. Search box is visible to users when they can enter text and click the search
button.
2. Program will convert entered text to XMl.
3. Send the XML data to the database.
4. Database.

Through the integration test, checks whether the data flows correctly which in this
case would be validating the XML files. Are the XML files generated correctly? Do
they have the correct data? Has the data been transferred correctly from one module
to another? All these things will be tested as part of Integration testing.

 Payment Functionality

INTERFACE TESTING
Used to check the data transfer between two components. This is a part of integration
testing. Interface testing includes testing of interfaces such as web services, APIs,
connection strings that connect two components in the application. These interfaces
don’t have a UI but takes an input and delivers output. Interface testing helps to
determine different functions like data transfer between the different elements in the
system are happening according to the way they were designed to happen.

The interface will pass the input to the payment service provider and returns an output
JSON file. The input file and output file with the requirements should be validate
through Interface Testing.
 Customers using different digital devices

COMPONENT TESTING
In this functional testing method, testing a module independently to verify its
expected output. Generally, component testing are done to verify the functionality or
usability of a component but not restricted only for that. A component can be of
anything which can take inputs and deliver desired output.

Testing the UI part for Usability and Accessibility – The UI design should be checked
whether it is compatible for different screens. Should check all the alignments are
appropriate for different screens.

 Geographical location

USER ACCEPTANCE TESTING

This is the last phase of the software testing process. In User Acceptance Testing
actual software is tested by users to make sure it can handle the real world scenarios.

Generally, it is performed at the time of product delivery to customers as a final

checkpoint among all the functional testing types. When delivering the products,
geographical location is affected in many ways. The delivery location might be
located far from the outlets and they might be not in the districts which having the
outlets. By considering the current COVID-19 pandemic situation of the country
some areas might be lockdown, therefore we should make sure the products are
delivered on time.
3) Write 5 high priority test cases for above mention case study.
1. Home Page Test Cases

 Page loading speed.

 The links take the user to correct page.
 The expected time takes the user to log with the correct data.
 Standard (attractive) color coding and font for the home page.
 Sign up button, Log in button are easy to locate.

2. Registration and Login Test Cases

 Correct credentials entered by the user – User log into the account
 User clicks on registration button – registration form opens.
 User click on forgot password – a password change form opens.
 A user tries to log with invalid credentials – Pop-up a message with invalid
username and password.
 Logged user clicks on Sign out – the system logs off.

3. Search Functionality

 Check the search using a product name or category name.

 Results from subcategory are displayed if else is not specified.
 The items are not repeating.
 The most relevant products appear first.

4. Shopping Cart Test Cases

 Confirm if the item is added to the cart.

 Check the amount payable is correct.
 Items in the cart are displayed with correct names, quantity and price.
 Confirm if the delivery charges are added.
 Check the delivery date of the item.

5. Payment Functionality

 Check if the cash on delivery option is available or not.

 Check if the payment option credit card, debit card and net banking is given.
 Check if the bank offers are accepted in this process.
 If a certain payment comes with extra charges, the prices are correct.
4) Assume you figure out defect in login page. Once you enter correct
registered username and password system displays an error saying
“Please enter correct username or password”

 Define the defect.

Detailed description of the defect including information about the module in which
defect was found should be discussed with the relevant tested scenarios.

Defect in login page. Once the correct registered username and password is entered,
system displays an error message “Please enter the correct username and password”.
Further should be discussed whether this error message is display for all the registered
users or any relevant set of users.

 Actual results vs Expected results.

When registered username and password is entered.

Actual result: Error message
Expected result: Main page

And also should be focused whether this defect occurs in other versions as well.

 Discuss the severity of the bug.

Which describes the impact of the defect on the application.

 Discuss the priority on the problem.

Which is related to defect fixing urgency. Severity Priority could be High/ Medium/
Low based on the impact urgency at which the defect should be fixed respectively.

 Discuss the possible defects for the error.

Discuss among the developing team about the possible places where the system goes
wrong. May be a bug in the code, or database query. Either an issue when connecting
the database with the system.

Write a defect for the above mentioned error.

 The user will be able to register for the system successfully (the relevant
database query is working) But when the user tries to log into the system for
the correct registered username and password it will display an error message.
This may occur due to incorrect database query. Query of retrieving data from
database may will not correct.