GROUP 4 March 12, 2023

FUNCTIONAL
TESTING PLAN
FOR ACCENTURE PHILIPPINES
INTRODUCTION
The project is an E-commerce (car
parts), also known as internet
commerce, project that communicates
with its clients online via its app and
website. It offers the consumers or
users the convenience to shop online
by providing a list of various products
that may be bought in the store. The
project is a B2C retail business concept
where goods or services are delivered
directly to customers.

 TEST OBJECTIVES
• Authentication: User can signup/login/logout.

User can view lists of items for sale and search by name, and filter by
price.
User adds products to their shopping cart, and the app remembers
them for the subsequent login.

Items in the shopping cart can be deleted by the user.

User-friendly interface.

Renders product data, categories, and site information for user display.
Item quantity can be edited by the
user.
Order Configuration.
 BUILD 1
FEATURES
TO BE 1. Authentication

TESTED 1.1 Signup 1.2 Login

• Username • Email filed

• Email fields • Password
• Password • Login form
• Terms and conditions • Error message
• Confirmation Message • Success message
• Redirect to the Login Page
 BUILD 1
FEATURES
TO BE 2. Product Filter

TESTED 2.1 Filter Results

• Name
• Price
• Demand

2.2 Search Results

2.3 Verify Values
2.4 Verify Selected Filter can be cleared
2.5 Filter UI works properly
 BUILD 2
FEATURES
1. Add to Cart
TO BE
“Add-to-cart” button is clickable or not
TESTED User can add products to the cart or not, adding one item to the
cart and verifying.
Success message is displayed or not when a product is added to
the cart successfully
Checks added item is displayed in the cart
Cart total
Cart total when the admin end enables the exclusive tax
Cart total and its delivery fee
Product details page is open when the user clicks on the product
description on the checkout page.
 BUILD 2
FEATURES
TO BE 2. Delete Item - Cart

TESTED Message when the item is deleted from cart

Cart total when the item is deleted from cart
Cart after removing all items in the cart
 BUILD 3
FEATURES
TO BE 1. Edit Item - Cart

TESTED Increment in Item quantity if user add plus button

Increment in Cart total in adding item quantity
Adding multiple items of different types and verify

2. Order Configuration

Validation of Mode of Payment

Payment Information
Payment Success Message
Payment Error Message
Address is complete
Success Message check out transaction complete
FEATURES NOT
TO BE TESTED
User-friendly Interface

Renders product data, categories,

and site information for user
display.
PASS/FAIL
CRITERIA

To pass the (Test), the following criteria must be met:

Authentication: User can signup/login/logout

User can view lists of items for sale and search by name, and filter by price.
User adds products to their shopping cart, and the app remembers them for the
subsequent login.
Items in the shopping cart can be deleted by the user.
User-friendly interface
Renders product data, categories, and site information for user display.
Item quantity can be edited by the user
Order Configuration
SUSPENSION CRITERIA
1. Normal Criteria

At the end of each day (4:00 p.m.) testing will be

suspended. At that time, all test cases executed during
the day should be marked as such. The system
integration test team will initiate a backup routine to save
the day’s updated test files. When all test cases have
been executed, the test will be suspended and the
results documented for the System Functional Test
Summary Report.
SUSPENSION CRITERIA
2. Abnormal Criteria
As a general guideline, if the defect backlog continually increases over a two-
week period, testing should be suspended. This will allow the developers time
to fix existing defects without the pressure and confusion of new defects being
added to the backlog. When a change is being migrated to the test
environment, the functional test team leader must be notified in advance to
schedule a time for the move. After the move has been completed, a retest of
previously tested functions should be performed. If a critical processing unit is
found to have severe defects (as defined by the defect reporting process),
testing should be suspended until the defects have been fixed. When the fixed
unit is moved back into the test environment, any previously performed tests
that affect the unit should be performed again to ensure new defects were not
created as a result of the fix.
 TEST ENVIRONMENT

Hardware Network

• MacBook Pro (16-inch, 2019) - Technical Specifications • Wi Fi

Processor 802.11ac Wi Fi wireless networking; IEEE 802.11a/b/g/n compatible

2.6GHz
6 core Intel Core i7, Turbo Boost up to 4.5GHz, with 12MB shared L3 cache
Configurable to 2.4GHz 8 core Intel Core i9, Turbo Boost up to 5.0GHz, with 16MB shared L3 cache

Storage

• 512GB SSD

• RAM
16GB of 2666MHz DDR4 onboard memory

• Graphics
AMD Radeon Pro 5300M with 4GB of GDDR6 memory and automatic graphics switching Intel UHD Graphics 630
Major Tasks
and
Deliverables
TEST TEAM
LEVEL OF
NAME TITLE INVOLVEMEN RESPONSIBILITIES
T

leading the team, planning and executing testing activities,

Team Leader – ensuring the quality of testing, collaborating with
Ish Nicole G. stakeholders, providing feedback to team members,
Independent Test 40 hrs/wk identifying and resolving issues related to testing, and
Abanilla
Team ensuring compliance with regulations and standards.

Assistant Team Supporting the Team Leader, coordinating testing activities,

Leader – providing technical guidance, assisting with quality
Miguel L. Cruz Independent Test 40 hrs/wk assurance, identifying and resolving issues, collaborating with
Team stakeholders, and ensuring compliance with regulations and
standards.
TEST TEAM
LEVEL OF
NAME TITLE INVOLVEMEN RESPONSIBILITIES
T

Jeremiah Paul L.
End user 40 hrs/wk Create and run test cases in order to verify financial controls.
Lorenze

Supporting the Team Leader, coordinating testing activities,

Erickson D. providing technical guidance, assisting with quality
End user assurance, identifying and resolving issues, collaborating with
Ceres 30 hrs/wk stakeholders, and ensuring compliance with regulations and
standards.
TEST TEAM
LEVEL OF
NAME TITLE INVOLVEMEN RESPONSIBILITIES
T

Reviewing requirements, developing test plans,

conducting tests, reporting defects, communicating with
Elijah P. Pascual Independent stakeholders, analyzing test results, and recommending
40 hrs/wk
Tester improvements to software development processes and
practices.

Reviewing requirements, developing test plans,

conducting tests, reporting defects, communicating with
Michael Jan S.
Independent stakeholders, analyzing test results, and recommending
Santiago 40 hrs/wk
Tester improvements to software development processes and
practices.
TEST TEAM
LEVEL OF
NAME TITLE INVOLVEMEN RESPONSIBILITIES
T

Reviewing requirements, developing test plans,

conducting tests, reporting defects, communicating with
Armando D.
Independent stakeholders, analyzing test results, and recommending
Cuasay 40 hrs/wk
Tester improvements to software development processes and
practices.

Reviewing requirements, developing test plans,

conducting tests, reporting defects, communicating with
Michael Jan S.
Independent stakeholders, analyzing test results, and recommending
Santiago 40 hrs/wk
Tester improvements to software development processes and
practices.
TEST TEAM
LEVEL OF
NAME TITLE INVOLVEMEN RESPONSIBILITIES
T

Reviewing requirements, developing test plans,

conducting tests, reporting defects, communicating with
stakeholders, analyzing test results, and recommending
improvements to software development processes and
Jeremy G. Flores
Developer 40 hrs/wk practices. Designing and developing software, writing
code, integrating systems, ensuring security, testing
and debugging, collaborating with stakeholders, and
maintaining documentation

Training -
https://www.udemy.com/course/learn-functional-testing-and-jira-from-scratch/ John Paul Genciane