Test Report (ID: TEM_TER, Version 4.1.

9, Classification: Confi

Test Report

UTec Marketplace

<Project Code>

<Product Name>

Document ID <SW/SYS>_<Unit/Module/Integration/Functional>Test Report_UTec Mark

Document Version Version #
Version Date
Version Date <dd-mm-yy>
 4.1.9, Classification: Confidential)

rt

lace

e>

me>

al>Test Report_UTec MarketPlace>

Tested Code Version
Build/Version
Test Type

Version Date
Version # Status <dd-mm-yy> Author

Note for Status:

Draft – The work product or CI is in development and not sent or shared for review. In this state, changes or modific
versions.
Reviewed – The work product is Reviewed. In this state, changes or modifications can be made to the document as
the versions.
Approved – The work product is Approved by an authorized person/s. Any change from this state requires a new re
 Approval Date
Reviewed By Approved By <dd-mm-yy>

nd not sent or shared for review. In this state, changes or modifications can be made to the document without repeatedly changing the

state, changes or modifications can be made to the document as per Review Comments from the Reviewer without repeatedly changing

uthorized person/s. Any change from this state requires a new revision.
 Description of the Modifications

the document without repeatedly changing the

from the Reviewer without repeatedly changing

 Test Report
To enable testers to document all test cases,
Purpose

The document contains list of all the change requests which are maintained by PM

Scope

This document is intended for Project Manager, Project Team (Dev & test Leads), senior m
requested then Customer (End Users).
Intended Audience

Abbreviations Full Forms / Definitions

UT Unit testing
MT Module testing
UTR Unit test report
MTR Module test report
SRS System requirement specificatio
SWRS Software requirement specificatio
HRS Hardware requirement specificati
PL Project lead
PM Project Manager

Reference documents
Number Reference version Document Name
 maintained by PM

Dev & test Leads), senior management, QA, and if

ull Forms / Definitions

Unit testing
Module testing
Unit test report
Module test report
m requirement specification
e requirement specification
re requirement specification
Project lead
Project Manager

Comments
Setup

Diagram

Add Diagram here for your setup.

Description

Give brief description of above diagram.

TMP 037 : Test Case

Test Cycle No.

Effort spent on Effort spent on Test Test Case Complexity
Total No.
Module Testcase Report Pass Fail
of T.C's High Medium Low
preperation(hrs) preperation(hrs)
Home Page Functionality 46 5 25 16 17 2
Header 19 0 11 8 18 0
Footer 22 4 18 0 7 0
Login & Logout 29 6 20 3 26 0
Buyer Onboarding-Registration 20 3 15 2 0 0
Seller Onboarding-Registration 16 1 9 6 5 0
Wishlist 13 3 6 4 8 0
Search Landing Page 12 1 3 8 0 0
PLP 34 0 22 12 0 0
PDP 32 4 23 4 0 0
Cart Management 25 1 16 8 0 0
Checkout 31 30 0 0 0 0
Shipping Charges 49 45 4 0 0 0
Delivery Method 23 5 13 5 0 0
My Account 39 6 22 11 0 0
Seller Panel 50 4 34 12 0 0
Admin Panel 69 42 26 1 0 0
Seller Catalog Management 22 1 13 8 0 0
RFQ Management 25 0 18 7 0 0
Invoicing Management 21 0 15 6 0 0
Payout Management 20 4 12 4 0 0
Price Management 26 1 25 0 0 0
RMA(Return Merchandise Authorization) 26 7 19 0 0 0
Total 669 173 369 125 81 2

TMP 037 : Test CaseVersion No:3.0 Release Date: September 8, 2010CONFIDENTIAL 10

TMP 037 : Test Case

Test Cycle No. 1

Not A
Not Executed Test Date
Bug
27
1
15
3
20
11
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
82

TMP 037 : Test CaseVersion No:3.0 Release Date: September 8, 2010CONFIDENTIAL 11

 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_HP_001
Verify personalized
Integration MC-130 recommendations for
user

UT_HP_002
Verify fallback to
Integration MC-130 trending products for
new users

UT_HP_003
Check
Integration MC-130 recommendations
after a new purchase

UT_HP_004
Verify
Integration MC-130 recommendations for
logged-out users

UT_HP_005
Check behaviour after
Integration MC-130 clearing browsing
history

UT_HP_006
Verify category
Integration MC-131 navigation from home
page

UT_HP_007
Verify message when
Integration MC-131 no products in
category
UT_HP_008
Verify L2 navigation
Integration MC-131 from L1 category
page

UT_HP_009
Check L3 navigation
Integration MC-131 from L2 category
page

UT_HP_010

Verify breadcrumbs
Integration MC-131 for category
navigation

UT_HP_011
Verify autocomplete
Integration MC-132 suggestions in global
search

UT_HP_012

Verify search results

Integration MC-132 can be filtered by
category

UT_HP_013
Verify no matching
Integration MC-132 products message is
displayed

UT_HP_014

Verify search
Integration MC-132 suggestions include
categories/brands

UT_HP_015

Verify filter
Integration MC-132 functionality works
after searching
UT_HP_016

Verify recently
purchased products
Integration MC-133
are displayed in
carousel

UT_HP_017
Verify no carousel is
Integration MC-133 displayed if no
previous purchases

UT_HP_018

Verify carousel
Integration MC-133 navigation
functionality

UT_HP_019

Verify product details

Integration MC-133 in recently purchased
carousel

UT_HP_020
Verify default
Integration MC-133 message when no
purchases made

UT_HP_021
Verify best-selling
Integration MC-134 products are
displayed

UT_HP_022
Verify seasonal
Integration MC-134 products are
displayed

UT_HP_023

Verify handling of no
Integration MC-134 trending/best-selling
products
UT_HP_024

Verify list updates

Integration MC-134 during seasonal
events

UT_HP_025
Verify quick links are
Integration MC-134 displayed on the
home page

UT_HP_026
Verify navigation
Integration MC-135 through quick links
(e.g., RFQ)

UT_HP_027
Verify navigation
Integration MC-135 through quick links
(e.g., Orders)

UT_HP_028
Verify navigation
Integration MC-135 through quick links
(e.g., FAQ)

UT_HP_029
Verify quick links are
Integration MC-135 functional for static
pages

UT_HP_030 MC-129 Verify dynamic

banners are displayed
based on user
System preferences and
history.

UT_HP_031 MC-129 Verify if active

promotions are
System reflected in dynamic
banners on the site.
UT_HP_032 MC-129 Check that default
banners are shown to
System logged-out users,
prompting them to log
in.
UT_HP_033 MC-129 Validate that banners
update according to
System time-sensitive
campaigns.
UT_HP_034 MC-129 Verify that clicking on
a banner redirects to
System the relevant product
or category page.
UT_HP_035 MC-129 Confirm standard
banners are shown
System when there are no
active promotions.
UT_HP_036 MC-129 Ensure fallback
content is displayed if
System there’s an error in
loading banners.
UT_HP_037 MC-51 Verify if ystem
displays the default
System Pincode configured in
the backend.

UT_HP_038 MC-51 Verify if system

accepts the Pincode
and displays a list of
System products available in
the entered location.

UT_HP_039 MC-51 Verify if ystem

displays an error
System message prompting
for a valid Pincode.

UT_HP_040 MC-51 Verify if system

prompts to enter a
Pincode and does not
System refresh the page.

UT_HP_041 MC-51 Verify if system

displays a message to
"Enter a serviceable
System Pincode".

UT_HP_042 MC-51 Verify if system

remembers the
Pincode and displays
products for the
System location without
prompting for re-
entry.

UT_HP_043 MC-51 Verify if system

displays a message
indicating the correct
Pincode format and
System prompts for a
correctly formatted
Pincode.
UT_HP_044 MC-51 Verify if System allows
input of new Pincode,
refreshes the page,
System and shows products
for the new Pincode.

UT_HP_045 MC-51 Verify if system

displays suggested
Pincodes based on
System previously added
addresses.

UT_HP_046 MC-51 Verify if System

displays an error
message stating
System "Unable to fetch
results, please try
again later."
 Total No. Of Test Cases : 46
High
Complexity Count :
5
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Open the home page.

2. Ensure the buyer is logged in. Buyer has a purchase and browsing
3. Observe the product recommendations history
section.

1. Open the home page.

2. Ensure the buyer is logged in. Buyer has no purchase or browsing
3. Observe the product recommendations history
section.

1. Make a new purchase or browse some new

product categories.
Buyer makes a new purchase or adds
2. Refresh the home page.
new items to browsing list
3. Observe the product recommendations
section.

1. Open the home page as a logged-out user.

2. Observe the product recommendations Buyer is logged out
section.

1. Clear the buyer's browsing history.

2. Reload the home page.
Buyer clears their browsing history
3. Observe the product recommendations
section.

1. Open the home page.

2. Click on any L1 category link.
3. Observe if the system navigates to the L1
Buyer is on the home page
category page.
4. Click on any L2 or L3 subcategory link and
verify navigation.
1. Open the home page.
2. Click on an L1, L2, or L3 category link with
Buyer selects a category with no
no available products.
available products
3. Observe the system's response after trying
to load the category.
1. Open the home page.
2. Navigate to an L1 category page.
3. Click on an L2 category from within the L1 Buyer is on an L1 category page
page.
4. Verify navigation to the L2 category page.

1. Open the home page.

2. Navigate to an L2 category page.
Buyer is on an L2 category page
3. Click on an L3 subcategory link.
4. Verify navigation to the L3 category page.

1. Open the home page.

2. Click on any L1 category.
3. From L1, navigate to an L2 category.
Buyer is navigating through L1, L2,
4. From L2, navigate to an L3 category.
and L3 categories
5. Verify that the breadcrumbs are displayed
and correctly represent the navigation
hierarchy.
1. Open the home page.
2. Click on the global search bar.
3. Type at least three characters. Buyer starts typing in the search bar
4. Observe the autocomplete suggestions
based on the input.
1. Enter a search query in the global search
bar.
2. Observe the search results page.
3. Apply filters such as category, price, and Buyer has entered a search query
ratings.
4. Verify that the filtered results are
displayed.
1. Enter a search query that does not match
any products. Buyer enters a search query with no
2. Execute the search. matching products
3. Observe the results page.

1. Open the home page.

2. Click on the global search bar.
3. Type a few characters.
Buyer starts typing in the search bar
4. Verify that the autocomplete suggestions
show product names, categories, and brands
based on the input.

1. Perform a search query.

2. Apply filters to the results.
3. Modify the search query in the search bar.
Buyer has modified a search query
4. Verify that the filters still function as
expected and update results according to the
new search query.
1. Open the home page.
2. Scroll to the "Recently Purchased" section.
3. Observe if a carousel of previously Buyer has made previous purchases
purchased products is displayed.
4. Verify that the carousel contains the
correct recently purchased products.

1. Open the home page.

2. Scroll to the "Recently Purchased" section.
3. Verify that no carousel is displayed. Buyer has not made any purchases
4. Observe if the section is either hidden or
replaced with a default message.

1. Open the home page.

2. Scroll to the "Recently Purchased"
carousel.
3. Use the next and previous buttons to Buyer has made previous purchases
navigate through the carousel.
4. Verify that the carousel allows the buyer to
scroll through all items smoothly.

1. Open the home page.

2. Scroll to the "Recently Purchased" section.
3. Observe the details displayed in the
Buyer has made previous purchases
carousel for each product.
4. Verify that product name, image, and
reorder option are visible for each item.

1. Open the home page.

2. Scroll to the "Recently Purchased" section.
3. Verify if the section shows a default Buyer has not made any purchases
message (e.g., "No recent purchases")
instead of the carousel.

1. Open the home page.

2. Scroll to the "Best-Selling Products"
section. Buyer is on the home page
3. Observe if a curated list of best-selling
products is displayed.

1. Open the home page.

2. Scroll to the "Seasonal Products" section. Buyer is on the home page during a
3. Observe if a curated list of seasonal seasonal event
products relevant to the current season or
event is displayed.

1. Open the home page.

2. Scroll to where the curated lists section is
expected to be. No trending or best-selling products
3. Observe if the system hides the section or available
displays a default message when no trending
or best-selling products are available.
1. Open the home page during a seasonal
event.
2. Scroll to the "Seasonal Products" section. Buyer is on the home page during a
3. Verify that the seasonal products list seasonal event
reflects the current season/event and
changes accordingly over time.

1. Open the home page.

2. Scroll through the page.
Buyer is on the home page
3. Observe if quick links to RFQ, Orders, FAQ,
and static pages are displayed.
1. Open the home page.
2. Click on the RFQ quick link.
Buyer is on the home page
3. Verify that the system navigates the buyer
to the RFQ page.
1. Open the home page.
2. Click on the Orders quick link.
Buyer is on the home page
3. Verify that the system navigates the buyer
to the Orders page.
1. Open the home page.
2. Click on the FAQ quick link.
Buyer is on the home page
3. Verify that the system navigates the buyer
to the FAQ page.
1. Open the home page.
2. Click on a quick link to a static page (e.g.,
Privacy Policy). Buyer is on the home page
3. Verify that the system navigates to the
respective static page.
1. Log in as a user with browsing/purchase
history.
2. Navigate to homepage or product category
page. Buyer is on the home page

1. Ensure active promotions exist.

2. Visit homepage or specific product pages.
Buyer is on the home page

1. Log out of the user account.

2. Browse products or categories.
Buyer is on the home page

1. Ensure a time-sensitive campaign is active.

2. Visit the platform during the campaign.
Buyer is on the home page

1. Navigate to the homepage where a

dynamic banner is displayed.
2. Click on the banner. Buyer is on the home page
1. Ensure no active promotions exist.
2. Visit the homepage.
Buyer is on the home page

1. Simulate a system issue causing banner

loading failure.
2. Visit the platform. Buyer is on the home page

1. Access the homepage.

2. Observe the Pincode field.
Buyer is on the home page

1. Enter a valid Pincode in the designated

field.
2. Click "Submit".
Buyer is on the home page

1. Enter an invalid or non-existent Pincode.

2. Click "Submit".
Buyer is on the home page

1. Leave the Pincode field empty.

2. Click "Submit".
Buyer is on the home page

1. Enter a valid Pincode outside the

serviceable area.
2. Click "Submit".
Buyer is on the home page

1. Access the homepage after entering a

Pincode.
2. Refresh the page or revisit.

Buyer is on the home page

1. Enter a Pincode with incorrect format (e.g.,

12345).
2. Click "Submit".

Buyer is on the home page

1. Click the option to update Pincode.
2. Enter a new valid Pincode.
3. Click "Submit".
Buyer is on the home page

1. Access the Pincode input area.

2. Observe the suggested Pincodes list.
Buyer is on the home page

1. Attempt to enter a Pincode when the

system is down.
2. Click "Submit".
Buyer is on the home page
 Medium Low
25 16

Test Device (for

Expected Results Test Data
mobile)

The system should display personalized

product recommendations based on the
NA Desktop
buyer's previous browsing and purchase
behaviour.

The system should display trending or

popular products instead of personalized
NA Desktop
recommendations, as the buyer does not
have any browsing or purchase history.

The system should update the personalized

product recommendations based on the NA Desktop
new purchase or browsing activity.

The system should not display personalized

product recommendations but should
NA Desktop
display general recommendations like
trending or popular products.

The system should display popular or

trending products, as the buyer's browsing
history has been cleared, but might still NA Desktop
show personalized items based on
purchase history.

The system should navigate the buyer to

the respective category page (L1, L2, or
NA Desktop
L3) displaying the products within that
category.

The system should display a message

stating, "No products available in this
NA Desktop
category" if there are no products in the
selected category.
The system should successfully navigate to
the L2 category page, displaying the NA Desktop
relevant subcategory products.

The system should successfully navigate to

the L3 category page, displaying the
NA Desktop
relevant products or message if no
products are available.

Breadcrumbs should be displayed correctly

showing the path (e.g., Home > L1 > L2 >
NA Desktop
L3) for the categories the buyer navigates
through.

The system should display relevant

autocomplete suggestions based on
product names, categories, or brands as NA Desktop
the buyer types at least three characters in
the search bar.

The system should allow the buyer to filter

search results by categories, price, ratings,
NA Desktop
and other available filters, and the results
should update accordingly.

The system should display a message

stating, "No matching products found" if
NA Desktop
there are no products matching the search
query.

The system should provide autocomplete

suggestions that include product names,
NA Desktop
categories, and brands, helping the buyer
find products more efficiently.

The system should retain the filtering

functionality and adjust the filtered results
based on any modifications to the search NA Desktop
query, without requiring the buyer to
reapply filters.
The system should display a carousel of
the buyer's recently purchased products,
NA Desktop
providing quick access to reorder
frequently bought items.

The system should not display a recently

purchased products carousel if the buyer
has not made any purchases. The section NA Desktop
should either be hidden or display a default
message such as "No recent purchases."

The carousel should allow the buyer to

navigate through all recently purchased
NA Desktop
products using the next and previous
buttons, displaying each item correctly.

The products in the recently purchased

carousel should display relevant details,
including product name, image, and an NA Desktop
easy-to-access reorder option for each
item.

When no purchases have been made, the

system should display a default message
like "You haven't made any recent NA Desktop
purchases" or similar, in place of the
recently purchased products carousel.

The system should display a curated list of

best-selling products on the home page, NA Desktop
allowing buyers to discover popular items.

The system should display a curated list of

seasonal products relevant to the current
NA Desktop
season or event, helping the buyer
discover items suited to the season.

The system should hide the curated lists

section or display a default message, such
NA Desktop
as "No trending or best-selling products
available" if there are no such products.
The system should dynamically update the
seasonal products list to reflect the
ongoing season or event, allowing buyers NA Desktop
to discover relevant products based on
current trends.

The system should display quick links to

popular pages (RFQ, Orders, FAQ, etc.) on NA Desktop
the home page for easy access.

The system should successfully navigate

the buyer to the RFQ page upon clicking NA Desktop
the RFQ quick link.

The system should successfully navigate

the buyer to the Orders page upon clicking NA Desktop
the Orders quick link.

The system should successfully navigate

the buyer to the FAQ page upon clicking NA Desktop
the FAQ quick link.

The system should navigate to the correct

static page when the buyer clicks on a
NA Desktop
quick link to static pages (e.g., Terms of
Service, Privacy Policy).

Dynamic banners related to user’s past

activity, preferences, or location are NA Desktop
displayed.

1. Ensure active promotions exist.

2. Visit homepage or specific product NA Desktop
pages.

Default banners targeting a broad

audience are displayed, with a prompt to NA Desktop
log in for personalized promotions.

Banners reflect specific promotions and

countdown timers; revert to standard NA Desktop
promotions after the campaign ends.

User is redirected to the relevant product

or category page associated with the
banner's promotion or offer. NA Desktop
Standard banners with general marketing
content or placeholders are displayed, with
no expired or irrelevant promotions. NA Desktop

Fallback content or default banners are

displayed, and an error log is generated for
the admin team. NA Desktop

The system displays the default Pincode

configured in the backend.
NA Desktop

System accepts the Pincode and displays a

list of products available in the entered
location.
NA Desktop

System displays an error message

prompting for a valid Pincode.
NA Desktop

System prompts to enter a Pincode and

does not refresh the page.
NA Desktop

System displays a message to "Enter a

serviceable Pincode".
NA Desktop

System remembers the Pincode and

displays products for the location without
prompting for re-entry.

NA Desktop

System displays a message indicating the

correct Pincode format and prompts for a
correctly formatted Pincode.

NA Desktop
System allows input of new Pincode,
refreshes the page, and shows products for
the new Pincode.
NA Desktop

System displays suggested Pincodes based

on previously added addresses.
NA Desktop

System displays an error message stating

"Unable to fetch results, please try again
later."
NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
17 2 27 19

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium
Not Executed

Medium

Not Executed

Medium

Not Executed

Medium

Not Executed

Low

Not Executed

Medium

Pass

Low

Fail MC-332
Medium

Fail MC-339

Medium

Pass

Low

Pass

Medium

Pass

High

Not Executed Not yet full implemented

Low
Pass

Medium

Pass

High

Pass
Medium

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Low
Pass

Medium
Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Low

Pass

High
Pass

Low

Not Executed Not yet implemented

 Low
Pass

High
Pass

Low

Pass

Medium

Not Executed Not yet implemented

Low

Pass

Low

Pass

Medium

Pass

Medium

Not Executed Not yet implemented

Low

Pass
Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

High

Not Executed Not yet implemented

 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
41.30434782609 10.526315789474 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_HD_001
Verify that the page
refreshes when the
Unit MC-164
user clicks on the
Utec by UltraTech icon

UT_HD_002
Verify no action when
Unit MC-164 clicking outside the
Utec by UltraTech icon

UT_HD_003
Verify the page
refresh functionality
Unit MC-164
on different platform
pages

UT_HD_004 Verify the default

display of ‘All
Integration MC-165
Categories’ in the
search bar
UT_HD_005
Verify changing
categories in the
Integration MC-165
dropdown for search
filtering

UT_HD_006
Verify search
functionality without
Integration MC-165
changing category
selection

UT_HD_007 Verify the system’s

behaviour for an
Unit MC-165
invalid or empty
search query
UT_HD_008
Verify display of
Integration MC-166
default PIN code

UT_HD_009

Verify changing the

Integration MC-166
PIN code

UT_HD_010

Verify error message

Integration MC-166 for invalid PIN code
entry

UT_HD_011 Verify display of

Unit MC-167 'Login' option for
logged-out users
UT_HD_012 Verify display of 'My
Integration MC-167 Account' option for
logged-in users
UT_HD_013
Verify error message
Integration MC-167 for invalid login
attempt

UT_HD_014
Verify redirect to
Integration MC-168
Wishlist page

UT_HD_015
Verify redirect to cart
Integration MC-168
page

UT_HD_016
Verify message for
Integration MC-168
empty Wishlist

UT_HD_017
Verify message for
Integration MC-168
empty cart

UT_HD_018
Verify overlapping
Integration MC-169 display of All
Categories CLP

UT_HD_019
Verify navigation to
Integration MC-169 selected category
from CLP
 Total No. Of Test Cases : 19
High
Complexity Count :
0
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Navigate to any page on the platform.

2. Locate the "Utec by UltraTech" icon on the
User is on any page of the platform.
left side of the header.
3. Click the icon.

1. Navigate to any page on the platform.

2. Locate any part of the header outside the
"Utec by UltraTech" icon. User is on any page of the platform.
3. Click any non-interactive area in the
header.
1. Navigate to multiple pages (e.g., product
page, checkout page, etc.).
2. Click the "Utec by UltraTech" icon on each User is on various platform pages.
page.
3. Observe the behaviour.
1. Navigate to the homepage.
2. Locate the search bar on the page.
User is on the homepage.
3. Observe the default text displayed inside
the search bar.

1. Navigate to any page with the search bar.

2. Click on the categories dropdown inside User is searching for a product.
the search bar.
3. Select a specific product category.
4. Enter a search term and submit.
1. Navigate to the search bar.
2. Do not change the ‘All Categories’
dropdown. User is performing a search.
3. Enter a search term.
4. Click the search icon.
1. Navigate to the search bar.
2. Enter an invalid or empty search term.
User enters an invalid or empty query
3. Click the search button.
4. Observe the system response.
1. Open the application.
2. Observe the homepage.
User is on the homepage
3. Check the area next to the search bar for
the displayed default PIN code.
1. Open the application.
2. Navigate to the homepage.
3. Click on the displayed PIN code next to the User is on the homepage
search bar.
4. Enter a new valid PIN code.
5. Confirm the change.
1. Open the application.
2. Navigate to the homepage.
3. Click on the displayed PIN code next to the
User is on the homepage and
search bar.
attempts to change PIN
4. Enter an invalid or non-serviceable PIN
code.
5. Attempt to confirm.
1. Open the application.
2. Ensure the user is logged out. User is not logged in
3. Click on the profile icon in the header.
1. Open the application.
2. Log in to the user account. User is logged in
3. Click on the profile icon in the header.
1. Open the application.
2. Click on the profile icon in the header.
3. Enter incorrect login credentials on the User is on the login page
login page.
4. Click on the login button.
1. Open the application.
2. Navigate to any page. User is logged in
3. Click on the Wishlist icon in the header.
1. Open the application.
2. Navigate to any page. User is logged in
3. Click on the cart icon in the header.
1. Open the application.
2. Ensure the user has no items in their
User has an empty Wishlist
Wishlist.
3. Click on the Wishlist icon in the header.

1. Open the application.

2. Ensure the user has no items in their cart. User has an empty cart
3. Click on the cart icon in the header.

1. Open the application.

2. Navigate to the homepage. User is on the homepage
3. Click on the "All Categories" option.

1. Open the application.

2. Click on the "All Categories" option to User has opened the All Categories
display the overlapping CLP. CLP
3. Select a specific category from the
displayed options.
 Medium Low
11 8

Test Device (for

Expected Results Test Data
mobile)

The page should refresh, or the user should

NA Desktop
be redirected to the homepage.

The page should not refresh, and no

NA Desktop
unintended actions should occur.

The icon should consistently refresh the

page or redirect to the homepage across NA Desktop
all different pages of the platform.

The search bar should display ‘All

Categories’ as the default inside the search NA Desktop
bar.

The user should be able to select a

category, and the system should return
NA Desktop
filtered search results for the selected
category.

The system should return search results

NA Desktop
across all product categories.

The system should display a message

indicating that no results were found or NA Desktop
that the search term cannot be empty.
The default PIN code (e.g., 400001) should
NA Desktop
be displayed next to the search bar.

The system should update the location to

the new PIN code and display products and NA Desktop
sellers available for that PIN code.

The system should display an error

message indicating that the entered PIN NA Desktop
code is not valid or serviceable.

The system should display a ‘Login’ option

and redirect the user to the login page NA Desktop
when clicked.
The system should display ‘My Account’
and redirect the user to their account NA Desktop
details page when clicked.

The system should display an error

message indicating that the credentials are
NA Desktop
incorrect (e.g., "Invalid username or
password.").

The system should redirect the user to the

NA Desktop
Wishlist page, displaying all saved items.

The system should redirect the user to the

cart page, displaying all items added to the NA Desktop
cart.

The system should display a message

indicating that the Wishlist is empty (e.g., NA Desktop
"Your Wishlist is empty.").

The system should display a message

indicating that the cart is empty (e.g., NA Desktop
"Your cart is empty.").

The system should display the Category

Landing Page (CLP) overlapping the header
NA Desktop
and banner, allowing for easy browsing of
all categories.

The system should navigate the user to the

selected category page, displaying NA Desktop
relevant products for that category.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
18 0 1 18

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Pass

Low

Pass

Medium

Pass

Low
Pass

Medium

Pass

Medium

Pass

Low
Pass
 Low
Pass

Medium

Not Executed Not yet implemented

Medium

Pass

Low
Pass

Medium
Pass

Medium

Pass

Low
Pass

Low
Pass

Medium
Pass

Medium
Pass

Medium
Pass

Low

Pass
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
94.73684210526 0 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_FT_001 Verify Utec by

UltraTech contact
details are
Integration MC-170 displayed in the
footer.

UT_FT_002 Verify Social media

icons in the footer
function correctly
displayed.
Integration MC-170

UT_FT_003 Verify System

handles errors in
social media page
Unit MC-170 loading

UT_FT_004 Verify "Find It Fast"

section shows quick
Integration MC-171 links in the footer

UT_FT_005 Verify Clicking a link

in the "Find It Fast"
section navigates
Integration MC-171 the user to the
appropriate page.
UT_FT_006 Verify Error
handling for broken
links in "Find It Fast"
Unit MC-171 section.

UT_FT_007 Verify Redirect

logged-in users to
their account page
Integration MC-172 from the footer.

UT_FT_008 Verify Redirect

logged-out users to
the login page when
Integration MC-172 accessing "My
Account."

UT_FT_009 Verify Redirect

users to order
tracking page from
the footer.
Integration MC-172

UT_FT_010 Verify Handle errors

during order
Integration MC-172 tracking.

UT_FT_011 Verify Redirect

users to customer
service page from
the footer.
Integration MC-172

UT_FT_012 Verify Utec by

UltraTech contact
details are
Integration MC-170 displayed in the
footer.
UT_FT_013 Verify Social media
icons in the footer
function correctly
displayed.
Integration MC-170

UT_FT_014 Verify System

handles errors in
social media page
Unit MC-170 loading

UT_FT_015 Verify "Find It Fast"

section shows quick
Integration MC-171 links in the footer

UT_FT_016 Verify Clicking a link

in the "Find It Fast"
section navigates
Integration MC-171 the user to the
appropriate page.

UT_FT_017 Verify Error

handling for broken
links in "Find It Fast"
Unit MC-171 section.

UT_FT_018 Verify Redirect

logged-in users to
their account page
Integration MC-172 from the footer.

UT_FT_019 Verify Redirect

logged-out users to
the login page when
Integration MC-172 accessing "My
Account."
UT_FT_020 Verify Redirect
users to order
tracking page from
the footer.
Integration MC-172

UT_FT_021 Verify Handle errors

during order
Unit MC-172 tracking.

UT_FT_022 Verify Redirect

users to customer
service page from
the footer.
Integration MC-172
 Total No. Of Test Cases : 22
High
Complexity Count :
4
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1.Navigate to any page of the website.

2.Scroll to the bottom of the page where
the footer is located.
3.Check for the contact information in NA
the footer.

1.Scroll to the footer section on any

page.
2.Click on any of the social media icons
(e.g., Facebook, Instagram, LinkedIn).
3.Verify that a new tab is opened, NA
directing the user to the corresponding
social media page.

1.Scroll to the footer section on any

page.
2.Click on a social media icon (with a
broken link). NA
3.Check for error handling when the page
does not load.
1.Scroll to the footer section on any
page.
2.Check for the display of quick links in NA
the "Find It Fast" section
1.Scroll to the footer section on any
page.
2.Click on any of the links in the "Find It
Fast" section NA
3.Verify that the system navigates to the
correct page
1.Scroll to the footer section on any
page.
2.Click on a broken or incorrect link in
the "Find It Fast" section. NA
3.Observe the system's response when
the page does not load.
1.Navigate to any page where the footer
is visible.
2.In the "Customer Care" section of the
footer, click on the "My Account" link. NA
3.Verify that the user is redirected to
their account page.

1.Navigate to any page where the footer

is visible.
2.In the "Customer Care" section of the
footer, click on the "My Account" link. NA
3.Verify that the system redirects the
user to the login page.

1.Navigate to any page where the footer

is visible.
2.In the "Customer Care" section of the
footer, click on the "Order Tracking" link.
3.Verify that the user is redirected to a NA
page displaying the tracking information
for their ongoing order

1.Navigate to the footer and click on the

"Order Tracking" link.
2.Observe the system's response when NA
there is an error retrieving the order
tracking information.
1.Navigate to any page where the footer
is visible.
2.In the "Customer Care" section of the
footer, click on the "Customer Service"
link. NA
3.Verify that the system redirects the
user to a page where they can contact
customer service

1.Navigate to any page of the website.

2.Scroll to the bottom of the page where
the footer is located.
3.Check for the contact information in NA
the footer.
1.Scroll to the footer section on any
page.
2.Click on any of the social media icons
(e.g., Facebook, Instagram, LinkedIn).
3.Verify that a new tab is opened, NA
directing the user to the corresponding
social media page.

1.Scroll to the footer section on any

page.
2.Click on a social media icon (with a
broken link). NA
3.Check for error handling when the page
does not load.
1.Scroll to the footer section on any
page.
2.Check for the display of quick links in NA
the "Find It Fast" section
1.Scroll to the footer section on any
page.
2.Click on any of the links in the "Find It
Fast" section NA
3.Verify that the system navigates to the
correct page
1.Scroll to the footer section on any
page.
2.Click on a broken or incorrect link in
the "Find It Fast" section. NA
3.Observe the system's response when
the page does not load.
1.Navigate to any page where the footer
is visible.
2.In the "Customer Care" section of the
footer, click on the "My Account" link. NA
3.Verify that the user is redirected to
their account page.

1.Navigate to any page where the footer

is visible.
2.In the "Customer Care" section of the
footer, click on the "My Account" link. NA
3.Verify that the system redirects the
user to the login page.
1.Navigate to any page where the footer
is visible.
2.In the "Customer Care" section of the
footer, click on the "Order Tracking" link.
3.Verify that the user is redirected to a NA
page displaying the tracking information
for their ongoing order

1.Navigate to the footer and click on the

"Order Tracking" link.
2.Observe the system's response when NA
there is an error retrieving the order
tracking information.
1.Navigate to any page where the footer
is visible.
2.In the "Customer Care" section of the
footer, click on the "Customer Service"
link. NA
3.Verify that the system redirects the
user to a page where they can contact
customer service
 Medium Low
18 0

Test Device (for

Expected Results Test Data
mobile)

The contact details (office address,

phone number, email) for Utec by
UltraTech should be visible on the left
side of the footer. NA Desktop

The correct social media page is

opened in a new tab for the clicked
icon.

NA Desktop

The system displays an error message

notifying the user: "Unable to load the
page. Please try again later."
NA Desktop

"Find It Fast" section should shows

quick links in the footer
NA Desktop

"Find It Fast" section should be

navigates the user to the appropriate
page.
NA Desktop
The system should displays a 404 error
page or a user-friendly message

NA Desktop

The system should redirects the user

to their account page where they can
manage their details, orders, etc.
NA Desktop

The system should redirects the user

to the login page, prompting them to
log in to access their account.
NA Desktop

The system redirects the user to the

order tracking page where they can
view the status of their ongoing orders.

NA Desktop

The system should displays a message

notifying the user of the error.
NA Desktop

The system should redirects the user

to a customer service page where they
can access resources for support or
contact the customer service team.
NA Desktop

The contact details (office address,

phone number, email) for Utec by
UltraTech should be visible on the left
side of the footer. NA Desktop
The correct social media page is
opened in a new tab for the clicked
icon.

NA Desktop

The system displays an error message

notifying the user: "Unable to load the
page. Please try again later."
NA Desktop

"Find It Fast" section should shows

quick links in the footer
NA Desktop

"Find It Fast" section should be

navigates the user to the appropriate
page.
NA Desktop

The system should displays a 404 error

page or a user-friendly message

NA Desktop

The system should redirects the user

to their account page where they can
manage their details, orders, etc.
NA Desktop

The system should redirects the user

to the login page, prompting them to
log in to access their account.
NA Desktop
The system redirects the user to the
order tracking page where they can
view the status of their ongoing orders.

NA Desktop

The system should displays a message

notifying the user of the error.
NA Desktop

The system should redirects the user

to a customer service page where they
can access resources for support or
contact the customer service team.
NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
7 0 15 7

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

High

Pass

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium
Pass

Medium

Pass
Medium

Not Executed Not yet implemented

High

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

High

Pass
Medium

Not Executed Not yet implemented

Medium

Pass

Medium
Pass

Medium

Not Executed Not yet implemented

Medium

Pass

High

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
31.81818181818 0 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_LL_001 Verify Admin/Seller

should be able to
log in successfully
Integration MC-47 with valid
credentials

UT_LL_002 Verify Admin/Seller

login should fail
with an incorrect
Unit MC-47 username or
password.

UT_LL_003 Verify Admin/Seller

account should be
locked after
Integration MC-47 multiple incorrect
login attempts

UT_LL_004 Verify Admin/Seller

should be prompted
to fill in both the
Integration MC-47 username and
password fields.

UT_LL_005 Verify Admin/Seller

session should
expire after 1 hour
Integration MC-47 of inactivity
UT_LL_006 Verify Buyers should
not be able to
update their mobile
Integration MC-49 number and email
address from the
frontend

UT_LL_007 Verify Admin should

be able to update a
Buyer’s mobile
number or email
Integration MC-49
address from the
backend

UT_LL_008 Verify Admin should

be warned when
attempting to
Integration MC-49 change a Buyer’s
email address

UT_LL_009 Verify User should

be able to log out
Integration MC-48 successfully from
the system.

UT_LL_010 Verify User session

should
automatically expire
after inactivity for a
Integration MC-48 configurable time (1
hour by default).

UT_LL_011 Verify Guest users

should be prompted
to log in when
Integration MC-265 attempting to add
products to the cart.
UT_LL_012 Verify Guest users
should be prompted
to log in when
Integration MC-265 attempting to
request a quote
(RFQ)

UT_LL_013 Verify After

successfully logging
in via the popup,
Integration MC-265 the user's action
should proceed
automatically

UT_LL_014 Verify If a guest

user closes the login
Integration MC-265 popup, the action
should not proceed.

UT_LL_015 Verify System

should display an
Unit MC-265 error for invalid
login credentials.

UT_LL_016 Verify Logged-in

users should not
see the login popup
Integration MC-265 when adding to cart
or requesting an
RFQ.

UT_LL_017 Verify Guest users

should be able to
register via the
Integration MC-265 login popup when
adding to cart or
requesting RFQ.

UT_LL_018 Verify if OTP is

received via SMS to
Integration MC-46 the registered
number.
UT_LL_019 Verify if buyer is
logged in
successfully and
Integration MC-46
redirected to the
homepage.

UT_LL_020
Verify if Error
message indicates
the OTP is invalid
Unit MC-46
and prompts for re-
entry

UT_LL_021

Verify if message
displayed the OTP
Integration MC-46 has expired and
prompts to request
a new OTP.

UT_LL_022 Verify if new OTP is

sent via SMS, and
Integration MC-46 the buyer is
prompted to enter
it.
UT_LL_023 Verify if buyer is
logged out and
Integration MC-46 redirected to the
login page.

UT_LL_024 Verify if system

sends a new OTP
Integration MC-46 and prompts to
enter it.
UT_LL_025 Verify if user
session
automatically
Integration MC-50 expires, and user is
logged out from all
devices.

UT_LL_026 Verify if session

expiry time is
updated to 30
Integration MC-50 minutes in the
system.
UT_LL_027 Verify if user
session
automatically
Integration MC-50 expires, and user is
logged out.

UT_LL_028 Verify if session

expiry time is
updated to 2 hours
Integration MC-50 in the system.

UT_LL_029 Verify if user

session remains
active, as it is within
Integration MC-50 the new expiry time
of 2 hours.
 Total No. Of Test Cases : 29
High
Complexity Count :
6
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1.Navigate to the login page.

2.Enter a valid username for Admin or
Seller.
3.Enter the corresponding valid Buyer is on the home page
password.
4. Click on the "Login" button.
1.Navigate to the login page.
2.Enter an invalid username or password
for Admin or Seller.
3.Click on the "Login" button. Buyer is on the home page

1.Navigate to the login page.

2.Enter an invalid username or password
for Admin or Seller.
3.Repeat the login attempt with invalid Buyer is on the home page
credentials more than 3 times

1.Navigate to the login page.

2.Leave the username field blank or the
password field blank.
3.Click on the "Login" button. Buyer is on the home page

1.Log in as Admin or Seller.

2.Remain inactive for more than 1 hour.
3.Attempt to perform any action on the
dashboard (e.g., click a menu item or Buyer is on the home page
navigate to a different page).
1.Log in as a Buyer.
2.Navigate to the "Profile" or "Account
Settings" page.
3.Attempt to update the mobile number Buyer is on the home page
field.
4.Attempt to update the email address
field.

1.Log in as an Admin.
2.Navigate to the backend system and
search for the Buyer’s profile.
3.Open the Buyer’s profile and locate the
fields for mobile number and email NA
address.
4.Update the mobile number and email
address fields with valid data.
5.Save the changes.

1.Log in as an Admin.
2.Navigate to the backend system and
search for the Buyer’s profile.
3.Attempt to update the Buyer’s email NA
address field.
4.Save the changes.
1.Log in as Buyer/Admin/Seller.
2.Navigate to the dashboard.
3.Click the "Logout" button. Buyer is on the home page
4.Observe the behaviour after clicking
"Logout".
1.Log in as Buyer/Admin/Seller.
2.Stay inactive for more than 1 hour
(configurable).
3.Attempt to perform any action (e.g.,
click on a menu item, navigate to a new Buyer is on the home page
page).

1.Navigate to the product page as a

guest user.
2.Click the "Add to Cart" button.
Buyer is on the home page
1.Navigate to the product page as a
guest user.
2.Click the "RFQ" (Request for Quote)
button. Buyer is on the home page

1. As a guest user, click on "Add to Cart"

or "RFQ."
2. When the login popup appears, enter
valid login credentials and log in. Buyer is on the home page

1.As a guest user, click on "Add to Cart"

or "RFQ."
2.Close the login popup without logging Buyer is on the home page
in.

1.As a guest user, click on "Add to Cart"

or "RFQ."
2.In the login popup, enter invalid Buyer is on the home page
credentials (wrong email or password)
and click "Login."
1.As a logged-in user
(Buyer/Admin/Seller), click on "Add to
Cart" or "RFQ."
Buyer is on the home page

1.As a guest user, click on "Add to Cart"

or "RFQ."
2.When the login popup appears, choose
the "Register" option. Buyer is on the home page
3.Complete the registration process.

1. Navigate to the login page.

2. Enter the registered mobile number. Buyer is on the home page
3. Click "Submit".
1. Enter the correct OTP in the provided
field. Buyer gets otp
2. Click "Login".

1. Enter an incorrect OTP.

2. Click "Login".

Buyer gets otp

1. Wait until the OTP validity period

expires.
2. Enter the expired OTP.
3. Click "Login". Buyer gets otp

1. Click the "Resend OTP" button. Buyer requests an OTP but does
2. Wait for the new OTP to arrive. not receive it.

1. Remain inactive for more than 1 hour.

2. Attempt to perform any action (e.g.,
navigate to another page). Buyer is on the home page

1. Click the "Resend" button.

2. Wait for a new OTP. Buyer has requested an OTP but
did not receive it.

1. Log in as a regular user.

2. Remain inactive for 1 hour.

System is set to default session

expiry of 1 hour.

1. Navigate to session management Admin is logged in and has access

settings. to session management settings.
2. Change session expiry time to 30
minutes.
3. Save the changes.
1. Log in as a buyer user. Admin has modified the session
2. Remain inactive for 31 minutes. expiry time.

1. Navigate to session management Admin is logged in and has access

settings. to session management settings.
2. Change session expiry time to 2 hours.
3. Save the changes.

1. Log in as a regular user. Admin has modified the session

2. Remain inactive for 1 hour and 1 expiry time.
minute.
 Medium Low
20 3

Test Device (for

Expected Results Test Data
mobile)

Admin/Seller should be successfully

logged in and redirected to the
respective dashboard (Admin
Dashboard for Admin, Seller Dashboard NA Desktop
for Seller).

An error message should appear

indicating "Invalid username or
password"
NA Desktop

A message should display, indicating

that the account is locked

NA Desktop

message should display, indicating that

both fields are required

NA Desktop

A message should be displayed,

indicating the session has expired

NA Desktop
The mobile number and email address
fields should be non-editable

NA Desktop

The Buyer’s mobile number and/or

email address should be successfully
updated in the system

NA Desktop

Admin should be warned when

attempting to change a Buyer’s email
address
NA Desktop

User should be logged out from all

devices if logged in elsewhere.
NA Desktop

A message should appear indicating

the session has expired

NA Desktop

A login popup should appear with a

message: "To add the product to the
cart, please log in"
NA Desktop
A login popup should appear with a
message: "To submit an RFQ, please
log in.
NA Desktop

The product should automatically be

added to the cart, or the RFQ request
should be initiated after a successful
login. NA Desktop

The product should not be added to the

cart, and the RFQ request should not
be submitted. NA Desktop

An error message should display

saying, "Invalid login credentials.
Please try again." NA Desktop

The product should be added to the

cart, or the RFQ request should be
submitted without displaying the login
popup. NA Desktop

After successful registration, the

product should be automatically added
to the cart, or the RFQ request should
be submitted. NA Desktop

OTP is received via SMS to the

NA Desktop
registered number.
Buyer is logged in successfully and
NA Desktop
redirected to the homepage.

Error message indicates the OTP is

NA Desktop
invalid and prompts for re-entry

Message indicates the OTP has expired

and prompts to request a new OTP.

NA Desktop

New OTP is sent via SMS, and the

buyer is prompted to enter it.
NA Desktop

Buyer is logged out and redirected to

the login page or Homepage with not
logged in NA Desktop

System sends a new OTP and prompts

to enter it.
NA Desktop

User session automatically expires, and

user is logged out from all devices.

NA Desktop

Session expiry time is updated to 30

minutes in the system.

NA Desktop
User session automatically expires, and
user is logged out.

NA Desktop

Session expiry time is updated to 2

hours in the system.

NA Desktop

User session remains active, as it is

within the new expiry time of 2 hours.

NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
26 0 3 26

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

High

Pass

Medium

Pass

Medium

Pass

High

Pass

Medium

Pass
Medium

Not Executed Not yet implemented.

High

Pass

Medium

Not Executed Not yet implemented.

High

Pass

Medium

Pass

Medium

Pass
Medium

Not Executed Not yet implemented

Medium

Pass

High

Pass

Medium

Pass

High

Pass

Medium

Pass

Medium

Pass
Medium

Pass

Low

Pass

Low

Pass

Medium

Pass

Medium

Pass

Low
Pass

Medium

Pass

Medium

Pass
Medium

Pass

Medium

Pass

Medium

Pass
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
89.65517241379 0 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case Test Case

Test Case # Covered ID's
Type Description

UT_BO_001 Verify First-time

user successfully
verifies mobile
Integration MC-100 number via OTP.

UT_BO_002 Verify User enters

an incorrect OTP for
mobile verification
Unit MC-100

UT_BO_003 Verify User requests

OTP resend after
not receiving the
Integration MC-100 first OTP.

UT_BO_004 Verify New user

enters their name
and selects their
Integration MC-101 profession.

UT_BO_005 Verify User leaves

Unit MC-101 the profession field
empty
UT_BO_006 Verify User
encounters an error
Integration MC-101 while entering
details.
UT_BO_007 Verify User adds a
new site address
using a map
Integration MC-102 interface or live
location.

UT_BO_008 Verify User fails to

Integration MC-102 enter a valid site
address.
UT_BO_009 Verify User uses live
location to capture
Integration MC-102 the site address.

UT_BO_010 Verify User selects

their current
construction stage
System MC-103 from a dropdown
menu.

UT_BO_011 Verify User does

not select a
Integration MC-103 construction stage.

UT_BO_012 Verify User selects

an invalid or
unsupported option
Integration MC-103 for the construction
stage.

UT_BO_013 System identifies

dummy emails and
System MC-104 excludes them from
the notification list.

UT_BO_014 Verify The system

ensures no
System MC-104 notifications are
sent to dummy
emails.
UT_BO_015 Verify if Registration
is completed
successfully, and
the user is granted
access to the
platform.
System MC-196

UT_BO_016 Verify if system

prevents completion
and displays the
message: "Please
complete all
System MC-196 required fields to
proceed."

UT_BO_017 Verify if profile

fields (name,
profession, site
address, etc.)
Integration MC-197 should be auto-
populated with the
existing user’s
information.

UT_BO_018
Verify if system
should prompt the
user to update any
outdated or missing
System MC-197
information before
allowing them to
proceed.

UT_BO_019
Verify if system
should skip the
registration process
System MC-197 and prompt the user
to continue
shopping.
UT_BO_020

Verify if all profile

fields should be
auto-populated
System MC-197
accurately with the
existing user’s
information.
 Total No. Of Test Cases : 20
High
Complexity Count :
3
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1.Navigate to the mobile number login

screen.
2.Enter a valid mobile number.
3.Request OTP. NA
4.Enter the correct OTP received within
the valid time frame.
5.Submit the OTP.

1.Navigate to the mobile number login

screen.
2.Enter a valid mobile number.
3.Request OTP. NA
4.Enter the incorrect OTP
5.Submit the OTP
1.Navigate to the mobile number login
screen.
2.Enter a valid mobile number.
3.Request OTP. NA
4.Click the "Resend OTP" button.
5.Wait for the OTP to be resent.
1.Enter the user’s name in the name
field.
2.Select a profession from the dropdown
(Homeowner, Contractor, Architect, NA
Engineer).
3.Submit the details.
1.Enter a name but leave the profession
field empty. NA
2.Attempt to proceed.
1.Enter invalid characters or encounter a
technical issue while entering details.
2.Attempt to save the details. NA

1.Navigate to the site address login

screen.
2.Add a new site address manually or by
using the map interface. NA
3.Optionally add a Google Maps link.
4.Save the site address.
1.Enter an invalid site address.
2.Attempt to proceed. NA

1.Allow location permissions.

2.Use live location to capture the site
address. NA

1.Navigate to the construction stage

dropdown.
2.Select a construction stage
3.Save the selection. NA

1.Leave the construction stage dropdown

empty.
2.Attempt to proceed. NA

1.Select an invalid option from the

dropdown.
2.Attempt to proceed.
NA

1.Attempt to send an order confirmation

or marketing email.
2.Check the notification list. NA

1.Generate an order confirmation or

marketing email.
2.Attempt to send it to the dummy email. NA
1. Navigate to the registration page.
2. Enter valid mobile number and click
"Verify."
3. Enter required personal details (name,
email, password).
4. Add a valid site address (address line,
NA
city, postal code).
5. Select a construction stage from the
dropdown menu.
6. Click "Complete Registration."

1. Navigate to the registration page. The user is on the registration

2. Enter a valid mobile number but do page.
not click "Verify."
3. Leave personal details (name, email,
password) blank.
4. Leave the site address fields blank.
5. Do not select a construction stage.
6. Click "Complete Registration."

1. Navigate to the mobile verification User is registered

page.
2. Enter the registered mobile number
and click "Verify."
3. Input the verification code received via
SMS.
4. Click "Submit."
5. Navigate to the "My Profile" section.

1. Navigate to the mobile verification

page.
2. Enter the registered mobile number
and click "Verify." some information is missing or
3. Input the verification code received via outdated
SMS.
4. Click "Submit."
5. Navigate to the "My Profile" section.

1. Navigate to the mobile verification

page.
2. Enter the registered mobile number
and click "Verify." NA
3. Input the verification code received via
SMS.
4. Click "Submit."
1. Navigate to the mobile verification
page.
2. Enter the registered mobile number
and click "Verify."
3. Input the verification code received via NA
SMS.
4. Click "Submit."
5. Navigate to the "My Profile" section.
6. Check that all fields (name, profession,
site address, etc.) are correctly
populated.
 Medium Low
15 2

Test Device
Expected Results Test Data
(for mobile)

The mobile number is successfully

verified.

NA Desktop

An error message is displayed: "Invalid

OTP. Please try again."

NA Desktop

The OTP is resent, and a message is

displayed: "OTP sent again. Please
check your mobile."
NA Desktop

The user details should saved

successfully.

NA Desktop

An error message should be displayed:

"Please select a profession." NA Desktop
An error message is displayed: "Invalid
input. Please try again."
NA Desktop

The site address is saved successfully.

NA Desktop

An error message should be displayed:

"Please enter a valid address." NA Desktop

The system should automatically

captures and populates the user’s site
address. NA Desktop

The selected construction stage is

saved successfully.

NA Desktop

An error message is displayed: "Please

select your current home building
stage." NA Desktop

An error message is displayed: "Invalid

option. Please select a valid stage."

NA Desktop

The system excludes dummy email

addresses from the notification list.
NA Desktop

The system ensures that no

notifications are sent to dummy emails.
NA Desktop
Registration is completed successfully,
and the user is granted access to the
platform.

NA Desktop

The system prevents completion and

displays the message: "Please
complete all required fields to
proceed."

NA Desktop

The profile fields (name, profession,

site address, etc.) should be auto-
populated with the existing user’s
information.
NA Desktop

The system should prompt the user to

update any outdated or missing
NA Desktop
information before allowing them to
proceed.

The system should skip the registration

process and prompt the user to NA Desktop
continue shopping.
All profile fields should be auto-
populated accurately with the existing NA Desktop
user’s information.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 20 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

High

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

High

Not Executed Not yet implemented

Medium
Not Executed Not yet implemented
Medium
Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

High

Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for
test cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not
re-tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case
selected for test
cycle 2
Status
Actual Results (Regression Remarks
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case
selected for test
cycle 3
Bug ID Actual Results (Regression
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_SO_001 Verify Seller

initiates registration
Integration MC-91 with a registered
mobile number.

UT_SO_002 Verify Seller

attempts to register
Integration MC-91 with an
unregistered mobile
number.
UT_SO_003 Verify Seller’s
details are auto-
Integration MC-92 populated using
UTCL ID.

UT_SO_004 Verify the Auto-

populated fields
Integration MC-92 remain blank due to
missing data.
UT_SO_005 Verify Seller
successfully submits
Integration MC-93 the registration
form.
UT_SO_006 Verify Seller
attempts to submit
Integration MC-93 the form without
filling all mandatory
fields.
UT_SO_007 Verify Seller's
details are verified,
and the profile
Integration MC-94 status changes to
"Listed."

UT_SO_008 Verify Seller's GST

and PAN do not
Integration MC-94 match the sample
invoice.
UT_SO_009 Verify Seller’s
registration is
Integration MC-95 placed on hold for
further review.

UT_SO_010 Verify Seller

completes the
Integration MC-95 training, and the
status is updated.
UT_SO_011 Verify Seller fails to
Integration MC-95 attend the training
session.
UT_SO_012 Verify Seller
confirms terms and
Integration MC-96 conditions and goes
live.
UT_SO_013 Verify Seller
attempts to submit
Unit MC-96 without confirming
terms and
conditions.
UT_SO_014 Verify if system
displays only
serviceable
pincodes related to
the primary
Integration MC-97 pincode, and the
seller can select a
pincode.

UT_SO_015 Verify if system

displays pincodes
outside the
Integration MC-97 assigned province.
UT_SO_016 verify if system
prompts seller to
select at least one
Integration MC-97 pincode
 Total No. Of Test Cases : 16
High
Complexity Count :
1
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1.Navigate to the seller registration page.

2.Enter a registered mobile number.
3.Click on the "Register" button. NA

1.Enter an unregistered mobile number.

2.Click on the "Register" button.
NA

1.Access the seller registration form after

entering the UTCL ID.
2.Check if fields like UTCL Code, Email NA
Address, and Store Name are auto-
populated.
1.Access the seller registration form after
entering the UTCL ID.
2.Verify if any fields remain blank. NA

1.Fill in all mandatory fields in the

registration form.
2.Click on "Submit. "button NA

1.Leave one or more mandatory fields

empty.
2.Click on "Submit. "button NA
1.The onboarding team reviews the
submitted details
2.Verify if all details match the required
criteria. NA

1.Review the submitted GST and PAN

details.
2. Verify them against the sample NA
invoice.
1.The onboarding team identifies an
issue that requires further investigation.
2.Place the registration status on hold. NA

1.The seller completes the provided

training session.
2.The onboarding team reviews the NA
completion.
1.Verify whether the seller has attended
the training session. NA
2.Review the training progress.
1.The seller onboarding team approves
the submission.
2.Verify the confirmation of terms and NA
conditions.
1.Click on submit the final approval form
without checking the terms and
conditions box. NA

1. Log in to the seller account. Seller is registered. Seller's

2. Navigate to SKU management. primary pincode is stored.
3. Click "Select Pincode".
4. Verify the list of available pincodes.
5. Confirm only pincodes related to
primary pincode are visible.
6. Select a serviceable pincode using the
checkbox.
7. Save changes.

1. Log in to the seller account. Seller is registered. Seller's

2. Navigate to SKU management. primary pincode is stored.
3. Click "Select Pincode".
4. Attempt to view pincodes outside
assigned province.
5. Verify system response.
1. Log in to the seller account. Seller is managing SKUs.
2. Navigate to SKU management.
3. Click "Select Pincode".
4. Do not select any pincode.
5. Attempt to save changes.
 Medium Low
9 6

Test Device (for

Expected Results Test Data
mobile)

The registration is initiated successfully

NA Desktop

An error message should be displayed:

"Mobile number not recognized."
NA Desktop

The UTCL Code, Email Address, and

Store Name fields are auto-populated
and non-editable. NA Desktop

The auto-populated fields should

remain blank.
NA Desktop

The seller is notified that the

submission is successful.
NA Desktop

The form should not submitted until all

mandatory fields are completed.
NA Desktop
The profile status should changes to
"Listed."

NA Desktop

The seller's application is marked for

rejection.
NA Desktop

The status should changes to

"Pending."
NA Desktop

The onboarding team marks the status

as "Training Completed."
NA Desktop

The status remains as "Training in

Progress." NA Desktop

The seller's status should changes to

"Active."
NA Desktop

An error message should be displayed:

"You must confirm terms and
conditions before going live." NA Desktop

System displays only serviceable

pincodes related to the primary
pincode, and the seller can select a
pincode.

NA Desktop

System does not display pincodes

outside the assigned province.

NA Desktop
System should prompt seller to select
at least one pincode. Error message
should display indicating a pincode
must be selected. NA Desktop
 Cycle 1 _ Date: 26-09-2024
Total Not
Total Pass Total Fail Total Executed
Executed
5 0 11 5

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Pass

Low

Pass

Medium

Not Executed Not yet implemented

Low
Not Executed Not yet implemented

Medium
Pass

Low

Pass
 Low

Pass

Medium
Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Medium
Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium

Not Executed Not yet implemented

High

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
31.25 0 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_WL_001

Verify successful
Integration MC-247 addition of a product
to the Wishlist

UT_WL_002
Verify add to Wishlist
Integration MC-247 prompt for not logged-
in users

UT_WL_003
Verify prevention of
Integration MC-247 duplicate Wishlist
entries

UT_WL_004
Verify Wishlist icon
Integration MC-248 colour change after
adding to Wishlist

UT_WL_005
Verify if the user can
Integration MC-248 view the Wishlist with
saved items

UT_WL_006 Verify if the system

shows an empty
Integration MC-248
Wishlist when no
items exist
UT_WL_007
Verify if the system
Integration MC-249 handles Wishlist
loading errors
UT_WL_008
Verify if the user can
successfully remove
Integration MC-249
an item from the
Wishlist

UT_WL_009
Verify if the system
Integration MC-249 handles removing
unavailable items

UT_WL_010
Verify if the system
Integration MC-250 handles errors during
item removal

UT_WL_011
Verify successful
Integration MC-250 movement of an item
from Wishlist to cart

UT_WL_012
Verify behaviour when
Integration MC-250 moving an out-of-
stock item to cart

UT_WL_013
Verify price update
when moving an item
Integration MC-250
with a price change to
cart
 Total No. Of Test Cases : 13
High
Complexity Count :
3
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Log in to the account.

2. Browse products. User is logged in and browsing
3. Click on the "Add to Wishlist" button for a products
product.
4. Verify the product is added to the Wishlist
and a confirmation message is displayed.
1. Browse products.
2. Click on the "Add to Wishlist" button for a
product.
User is not logged in
3. Verify that the system prompts the user to
log in or sign up before adding the product to
the Wishlist.
1. Log in to the account.
2. Add a product to the Wishlist.
3. Try adding the same product again.
Product is already in the Wishlist
4. Verify that the system displays a
notification and prevents adding the product
again.
1. Log in to the account.
2. Browse products.
3. Click the "Add to Wishlist" button. User is logged in and browsing
4. Verify that the Wishlist icon changes products
colour, indicating that the product is now in
the Wishlist.

1. Log in as a user.
User has added items to their
2. Add items to the Wishlist.
Wishlist.
3. Navigate to the Wishlist page.

1. Log in as a user.
User has not added any items to the
2. Ensure no items are saved to the Wishlist.
Wishlist.
3. Navigate to the Wishlist page.

1. Log in as a user.
2. Simulate a system error (e.g., disconnect
System error occurs.
server or cause timeout).
3. Navigate to the Wishlist page.
1. Log in as a user.
2. Add items to the Wishlist.
3. Navigate to the Wishlist page. User has items in their Wishlist.
4. Click the "Remove" button next to a
product.
1. Log in as a user.
2. Add an item that is no longer available to
the Wishlist. The item is no longer available.
3. Navigate to the Wishlist page.
4. Click "Remove" next to the unavailable
item.
1. Log in as a user.
2. Add items to the Wishlist.
3. Simulate a system issue (e.g., disconnect System error occurs.
server or cause a timeout).
4. Try to remove an item.
1. Log in as a user.
2. Add items to the Wishlist.
3. Navigate to the Wishlist page. User has items in their Wishlist.
4. Click the "Move to Cart" button next to a
product.

1. Log in as a user.
2. Add an out-of-stock item to the Wishlist. The item is out of stock.
3. Navigate to the Wishlist page.
4. Attempt to move the out-of-stock item to
the cart.

1. Log in as a user.
2. Add an item to the Wishlist. The product price has changed.
3. Simulate a price change for the product.
4. Navigate to the Wishlist page.
5. Move the item to the cart.
 Medium Low
6 4

Test Device (for

Expected Results Test Data
mobile)

The system should add the product to the

Wishlist and display a confirmation NA Desktop
message like "Product added to Wishlist."

The system should prompt the user to log

in or create an account before adding a NA Desktop
product to the Wishlist.

The system should notify the user that the

product is already in the Wishlist and NA Desktop
prevent duplicate entries.

The Wishlist icon should change colour

(e.g., from grey to red) after a product is
NA Desktop
added to indicate that the product is in the
Wishlist.

The Wishlist page should display all saved

items with product details like name, price, NA Desktop
and availability.

The Wishlist page should show a message

indicating that the Wishlist is empty, NA Desktop
encouraging the user to browse products.

The user should see an error message and

NA Desktop
the system should suggest retrying later.
The item should be removed from the
Wishlist, and a confirmation message
NA Desktop
should appear indicating successful
removal.

The item should still be removed from the

Wishlist, and a message should notify the NA Desktop
user that the item is unavailable.

The user should see an error message, and

the system should log the issue for further NA Desktop
investigation.

The item should be removed from the

Wishlist and added to the cart. The user
NA Desktop
should be redirected to the cart page with
the item present.

The system should notify the user that the

item is out of stock and cannot be added to
NA Desktop
the cart. The item should remain in the
Wishlist.

The system should reflect the updated

price in the cart and notify the user of the
NA Desktop
price change. The item should be present
in the cart.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
8 0 5 8

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Pass

Medium

Pass

Low

Not Executed Not yet implemented

Low

Not Executed Not yet implemented

Medium
Pass

Low
Pass

High
Pass
Medium

Pass

Low

Not Executed Not yet implemented

High

Pass

Medium

Pass

Medium

Not Executed Not yet implemented

High

Not Executed Not yet implemented

 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
61.53846153846 0 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_SP_001 MC-52 Verify that search

results are displayed
Integration in a grid view with
product details.
UT_SP_002 MC-52 Verify that search
results are displayed
Integration in a grid view with
product details.
UT_SP_003 MC-52 Verify that search
results are displayed
Integration in a grid view with
product details.
UT_SP_004 MC-52 Verify that search
results are displayed
Integration in a grid view with
product details.
UT_SP_005 MC-52 Verify that pagination
controls appear when
Integration search results exceed
the limit.

UT_SP_006 MC-52 Verify that a message

is displayed when no
Integration products match the
search criteria.

UT_SP_007 MC-52 Verify that a loading

indicator appears
during slow
Integration network/Loading
Delays conditions.
UT_SP_008 MC-53 Verify that Add to Cart
and RFQ options are
not visible in search
Integration results.

UT_SP_009 MC-53 Verify that no Add to

Cart or RFQ options
Integration are mistakenly
displayed.

UT_SP_010 MC-53 Verify navigation to

Product Detail Page
Integration upon clicking a
product.

UT_SP_011 MC-53 Verify that clicking on

product details
Integration navigates to the
Product Detail Page.

UT_SP_012 MC-53 Verify that clicking on

a product that does
Integration not navigate results in
an error.
 Total No. Of Test Cases : 12
High
Complexity Count :
1
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Enter a valid product name in the search Buyer is logged in and has performed
bar. a search.
2. Click on the search button.
3. Observe the search results.
1. Enter a valid SKU in the search bar. Buyer is logged in and has performed
2. Click on the search button. a search.
3. Observe the search results.

1. Enter a single alphabet in the search bar. Buyer is logged in and has performed
2. Click on the search button. a search.
3. Observe the search results.

1. Enter more than 15 or 20 alphabets in the Buyer is logged in and has performed
search bar. a search.
2. Click on the search button.
3. Observe the search results.
1. Perform a search that returns more than Buyer has performed a search
20 products. returning multiple products
2. Observe the pagination controls at the
bottom.

1. Enter a non-existent product name in the Buyer is logged in and has searched
search bar. for a non-existent product.
2. Click on the search button.
3. Observe the results.

1. Simulate a slow network. Buyer is logged in and has performed

2. Perform a search. a search.
3. Observe the loading status.
1. Enter a valid product name in the search Buyer is logged in and has performed
bar. a search.
2. Click on the search button.
3. Observe the search results.

1. Perform a search that should return results Buyer is logged in and viewing search
without these options. results.
2. Observe the search results.

1. Click on a product in the grid. Buyer is in search landing page

2. Observe navigation to the Product Detail
Page.

1. Click on a product image or name in the Buyer is in search landing page

grid.
2. Observe navigation.

1. Click on a product image or name in the Buyer is in search landing page

grid.
2. Observe if any navigation occurs.
 Medium Low
3 8

Test Device (for

Expected Results Test Data
mobile)

Results are displayed in a grid view layout,

showing product image, name, price, and a NA Desktop
link to view details.

Results are displayed in a grid view layout,

showing product image, name, price, and a NA Desktop
link to view details.

Message "No Result." is displayed NA Desktop

Message "No Result." is displayed NA Desktop

Pagination controls are displayed, and

navigation between pages is functional.
NA Desktop

Message "No Result." is displayed NA Desktop

A loading spinner or message appears, and

search results are displayed in grid view
once available.
NA Desktop
Add to Cart and RFQ options are not
visible; only product details like image,
name, desc, price should be displayed
NA Desktop

Add to Cart and RFQ options should not be

visible
NA Desktop

Buyer is navigated to the Product Detail

Page where Add to Cart or RFQ options are
available. NA Desktop

Buyer is taken to the Product Detail Page

with full product information and Add to
Cart/RFQ options available. NA Desktop

If no navigation occurs, an error message

is displayed or a prompt to try again or
refresh the page appears. NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Low

Low

Low

Low

Medium

Low

High
 Low

Medium

Low

Low

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_PLP_001 MC-180 Verify that selecting a

category filters and
Integration displays the correct
products.

UT_PLP_002 MC-180 Verify that a message

is displayed when no
products are available
Integration in the selected
category

UT_PLP_003 MC-180
Verify that a message
is shown if there is an
Integration error loading the
category products.

UT_PLP_004 MC-180
Verify that the filter
options correctly filter
Integration
displayed products.

UT_PLP_005 MC-180 Verify that 2 or more

filter options correctly
Integration filter displayed
products.

UT_PLP_006 MC-180 Ensure that sorting

options correctly sort
Integration the displayed
products.
UT_PLP_007 MC-180
Verify that the "show"
options correctly limit
Integration the number of
displayed products.

UT_PLP_008 MC-180
Verify that pagination
controls allow
Integration navigation between
product pages.

UT_PLP_009 MC-180
Verify UI elements for
filters, sort by, show,
and pagination are
Unit
consistent in design
w.r.t. the wireframes

UT_PLP_010 Verify that selecting a

price range filters and
Integration MC-181 displays the correct
products.

UT_PLP_011
Verify that a message
is displayed when no
products are available
Integration MC-181
in the selected price
range

UT_PLP_012
Verify that the system
resets the price range
Integration MC-181 filter and displays all
available products.

UT_PLP_013 Verify that the

"Starting From" price
is displayed for
Unit MC-182
products in a valid pin
code.

UT_PLP_014
Verify that a message
is displayed when
there are no sellers
Integration MC-182
for the entered pin
code.
UT_PLP_015 Verify that an error
message is shown
when there is an issue
Integration MC-182 retrieving price data.

UT_PLP_016 Verify that the

"Starting From" price
reflects the lowest
Integration MC-182 price among multiple
sellers for a valid pin
code.

UT_PLP_017 Verify that the

"Starting From" price
is displayed in the
Integration MC-182 correct currency
format.

UT_PLP_018 Verify that the

"Starting From" price
updates correctly
Integration MC-182 when the user
changes the pin code.

UT_PLP_019 MC-183 Verify that all key

elements are
Integration displayed on each
product card.

UT_PLP_020 MC-183 Verify that clicking the

Wishlist icon adds the
Integration product to the
Wishlist.

UT_PLP_021 MC-183 Verify that clicking the

share icon provides
Integration sharing options.

UT_PLP_022 MC-183 verify that clicking

"View Details"
Integration redirects to the
product detail page.

UT_PLP_023 MC-183 Verify that the

discount is displayed
Integration correctly on the
product card.
UT_PLP_024 MC-183 Verify that clicking the
Wishlist icon again
removes the product
Integration from the Wishlist.

UT_PLP_025 MC-183 Verify that clicking the

product image
Integration redirects to the
product detail page.

UT_PLP_027 MC-185 Verify that brand

logos scroll
Integration horizontally from right
to left.

UT_PLP_028 MC-185 Verify that all brand

logos are visible in the
Unit scrolling section.

UT_PLP_029 MC-185 Verify that there is

visual feedback when
Unit a brand logo is
clicked.
UT_PLP_030 MC-185 Verify that clicking a
brand logo navigates
to the filtered product
Integration view.

UT_PLP_031 MC-186 Verify that featured,

sale, and best sellers
Integration are displayed in three
columns.

UT_PLP_032 MC-186 Verify that clicking a

product in the
Featured column
Integration redirects to the PDP.

UT_PLP_033 MC-186 Verify that clicking a

product in the Sale
Integration column redirects to
the PDP.
UT_PLP_034 MC-186 Verify that clicking a
product in the Best
Sellers column
Integration redirects to the PDP.
UT_PLP_035 MC-186 Verify that a message
is displayed when
there are no featured
Integration or sale or Best seller
products.
 Total No. Of Test Cases : 34
High
Complexity Count :
0
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Navigate to the Product Listing Page. User is on the Product Listing Page
2. Select a category (L1, L2, or L3) from the (PLP).
navigation menu.
3. Observe the displayed products.

1. Navigate to the Product Listing Page. User is on the Product Listing Page
2. Select a category that has no products. (PLP).
3. Observe the message displayed.

User is on the Product Listing Page

1. Navigate to the Product Listing Page. (PLP).
2. Select a category.
3. Simulate an error in retrieving products.
4. Observe the error message.

User is on the Product Listing Page

1.. Navigate to the Product Listing Page. (PLP).
2. Select a filter option.
3. Observe the displayed products.

User is on the Product Listing Page

1.. Navigate to the Product Listing Page. (PLP).
2. Select 2 or more filter options.
3. Observe the displayed products.

User is on the Product Listing Page

1. Navigate to the Product Listing Page. (PLP).
2. Select a sort option (e.g., price, discount).
3. Observe the order of products.
 User is on the Product Listing Page
1. Navigate to the Product Listing Page. (PLP).
2. Select a show option (e.g., 5, 10, 15
items).
3. Observe the number of products displayed.

User is on the Product Listing Page

(PLP).
1. Navigate to the Product Listing Page.
2. Observe the pagination controls.
3. Click on the next page.

User is on the Product Listing Page

(PLP).

1. Navigate to the Product Listing Page.

2. Observe the design of filter, sort by, show,
and pagination elements.

User is on the Product Listing Page

1. Navigate to the Product Listing Page. (PLP).
2. Select a specific price range.
3. Observe the displayed products.

User is on the Product Listing Page

(PLP).
1. Navigate to the Product Listing Page.
2. Select a price range that has no products.
3. Apply the filter.
4. Observe the message displayed.

User is on the Product Listing Page

1. Navigate to the Product Listing Page. (PLP).
2. Apply a price range filter.
3. Remove the price range filter.
4. Observe the products displayed.

User is on the Product Listing Page

(PLP).
1. Enter a valid pin code.
2. Load the Product Listing Page.
3. Observe the displayed prices.

User is on the Product Listing Page

(PLP).
1. Enter a pin code with no sellers.
2. Load the Product Listing Page.
3. Observe the displayed message.
1. Enter a pin code. User is on the Product Listing Page
2. Simulate an error in fetching pin code- (PLP).
specific data.
3. Load the Product Listing Page.

1. Enter a valid pin code with multiple sellers. User is on the Product Listing Page
2. Load the Product Listing Page. (PLP).
3. Observe the displayed prices.

1. Enter a valid pin code. User is on the Product Listing Page

2. Load the Product Listing Page. (PLP).
3. Check the format of the displayed prices.

1. Enter a valid pin code. User is on the Product Listing Page

2. Load the Product Listing Page. (PLP).
3. Change the pin code.
4. Reload the PLP.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Observe the product cards. (PLP).

1. Load the Product Listing Page. User is on the Product Listing Page
2. Click on the Wishlist icon for a product. (PLP).
3. Observe confirmation message.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Click on the share icon on a product card. (PLP).
3. Observe the sharing options.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Click on the "View Details" button of a (PLP).
product.
3. Observe the redirection.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Check the discount displayed on a product (PLP).
card.
1. Load the Product Listing Page. User is on the Product Listing Page
2. Click on the Wishlist icon for a product that (PLP) with a product in Wishlist
is already in the Wishlist.
3. Observe confirmation message

1. Load the Product Listing Page. User is on the Product Listing Page
2. Click on the product image. (PLP).
3. Observe the redirection.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll past the product listings. (PLP).
3. Observe the brand logo section.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll to the brand logo section. (PLP).
3. Check visibility of logos.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll to the brand logo section. (PLP).
3. Click on a brand logo.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll to the brand logo section. (PLP).
3. Click on a brand logo.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll past the brand section. (PLP).
3. Observe the three-column section.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll to the three-column section. (PLP).
3. Click on a product in the Featured column.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll to the three-column section. (PLP).
3. Click on a product in the Sale column.

1. Load the Product Listing Page. User is on the Product Listing Page
2. Scroll to the three-column section. (PLP).
3. Click on a product in the Best Sellers
column.
1. Load the Product Listing Page. User is on the Product Listing Page
2. Ensure no featured or Sale or best seller (PLP).
products are available.
NOTE: This can be done from the backend
3. Scroll to the three-column section.
 Medium Low
22 12

Test Device (for

Expected Results Test Data
mobile)

Only products belonging to the selected

category should be displayed.
NA Desktop

Message "We can't find products matching

the selection." is displayed
NA Desktop

A message should be displayed, offering a

NA Desktop
retry option.

Only products that match the selected

NA Desktop
filter criteria are displayed.

Only products that match the selected

NA Desktop
filter criteria are displayed.

Products are sorted according to the

selected criteria (e.g., NA Desktop
ascending/descending price).
The number of products displayed matches
NA Desktop
the selected show option.

User is navigated to the next set of

products, and the page updates NA Desktop
accordingly.

All UI elements have consistent styles,

colours, fonts, and sizes throughout the NA Desktop
page.

Only products within the selected price

NA Desktop
range are displayed

Message "No products available in this

price range" is displayed, and the filter NA Desktop
option resets.

All available products are displayed after

NA Desktop
the filter is reset.

The "Starting From" price is displayed for

each product based on the lowest price NA Desktop
available for that product.

Message “No sellers available for this

NA Desktop
product in your pin code” is displayed.
Message “Unable to fetch price for this pin
code” is displayed, along with an option to
retry.
NA Desktop

The "Starting From" price shows the lowest

price from available sellers for each
product.
NA Desktop

Prices are displayed in the correct currency

format e.g., ₹2363.
NA Desktop

The "Starting From" price updates to

reflect the lowest prices for the new pin
code entered.
NA Desktop

Each product card displays the product

name, image, small description. price,
special price (if any) discount, View Variant NA Desktop
link, Wishlist icon, and "View Details"
option.
The product is added to the user’s Wishlist,
and a confirmation message is displayed.
NA Desktop

The system displays sharing options (e.g.,

social media, email) for the product.
NA Desktop

The user is redirected to the product detail

page (PDP) of the selected
NA Desktop

The discount is displayed correctly in

percentage or amount
NA Desktop
The product is removed from the Wishlist,
and a confirmation message is displayed.
NA Desktop

The user is redirected to the product detail

page (PDP) of the selected product.
NA Desktop

Brand logos are displayed scrolling

horizontally from right to left; smoothly and
continuously without any stuttering or lag. NA Desktop

All brand logos are clearly visible without

any overlapping or cutoff.
NA Desktop

The clicked brand logo shows visual

feedback (e.g., highlight or animation)
indicating it has been selected. NA Desktop

The user is navigated to a new page or

section displaying only products from the
selected brand.
NA Desktop

Products are displayed under "Featured

Products," "Sale Products," and "Best
Sellers" in three separate columns. NA Desktop

The user is redirected to the product detail

page (PDP) of the selected product.
NA Desktop

The user is redirected to the product detail

page (PDP) of the selected product.
NA Desktop

The user is redirected to the product detail

page (PDP) of the selected product.
NA Desktop
The system should display a message
indicating that no products are available in
that category.
NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Low

Medium

Medium

Medium

Medium

Medium
 Low

Medium

Low

Low

Medium

Low

Medium

Low
Medium

Medium

Medium

Medium

Medium

Medium

Medium

Low

Medium
Medium

Low

Medium

Low

Medium

Medium

Medium

Low

Low

Low
Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_PDP_001 Verify that complete

product information is
displayed on the PDP
Integration MC-198

UT_PDP_002 Verify that clicking a

product on the PLP
Integration MC-198 redirects to the PDP.

UT_PDP_003 Verify that an out-of-

stock message is
Integration MC-203 displayed on the PDP.

UT_PDP_004 Verify that all product

images are displayed
Integration MC-198 correctly on the PDP.

UT_PDP_005 Verify that available

variants like
size/colour etc are
Integration MC-203 displayed on the PDP.

UT_PDP_006 Verify that the

product information
displayed matches the
Integration MC-198 information on the
Magento Backend.
UT_PDP_007 Verify that an error
message is displayed
Integration MC-198 for products with
incomplete details.

UT_PDP_008 Verify that detailed

product specifications
Integration MC-198 are available on the
PDP.

UT_PDP_009 Verify that social

sharing options are
Integration MC-198 available on the PDP.

UT_PDP_010 Verify that a product

can be successfully
Integration MC-199 added to the cart.

UT_PDP_011 Verify that an error

message is shown
when required
Integration MC-199 attributes isn't
selected

UT_PDP_012 Verify that an error

message is displayed
for unavailable
Integration MC-199 product variants.

UT_PDP_013 Verify that the cart

count increments
Integration MC-199 after adding a
product.

UT_PDP_014 Verify that selected

attributes isn't added
Integration MC-199 to cart after an
unsuccessful add
attempt.
UT_PDP_015 Verify that multiple
quantities can be
Integration MC-199 added to the cart
correctly.

UT_PDP_016 Verify that items in

the cart persist across
Integration MC-199 sessions for logged-in
users.
UT_PDP_017 Verify that the
confirmation message
Integration MC-199 disappears after a
certain duration.

UT_PDP_018 Verify that different

user roles (guest vs.
logged-in user)
Integration MC-199 behave as expected.

UT_PDP_019 Verify that the system

handles adding a very
large quantity of a
Integration MC-199 product.

UT_PDP_020 Verify that the

reviews section
Integration MC-200 displays customer
reviews and ratings.

UT_PDP_021 Verify that an

appropriate message
Integration MC-200 is shown when there
are no reviews.

UT_PDP_022 Verify that reviews

can be filtered based
Integration MC-200 on user-selected
criteria.

UT_PDP_023 Verify that selecting

"most recent" sorts
Integration MC-200 reviews by submission
date.

UT_PDP_024 Verify that selecting

"highest rating" sorts
Integration MC-200 reviews by rating
value.

UT_PDP_025 Verify that the content

of each review is
Integration MC-200 displayed correctly.

UT_PDP_026 Verify that reviews

are paginated if there
Integration MC-200 are too many to
display at once.
UT_PDP_027 Verify that user
ratings are displayed
Integration MC-200 alongside each
review.

UT_PDP_028 Verify that responses

from the seller to
Integration MC-200 reviews are visible if
applicable.

UT_PDP_029 verify in Magento

Integration MC-200 admin can view the
posted reviews
UT_PDP_030 verify all newly posted
reviews by user
Integration MC-200 should be in pending
status
UT_PDP_031 verify admin when
admin approves
reviews
Integration MC-200

UT_PDP_032 verify when admin

selects not approved
reviews
Integration MC-200
 Total No. Of Test Cases : 32
High
Complexity Count :
4
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Navigate to the PLP. User is on PDP

2. Click on a product.
3. Observe the PDP.

1. Navigate to the PLP. user is on PLP

2. Click on a product.
3. Check the URL.

1. Click on an out-of-stock product from the User selects an out-of-stock product.

PLP.
2. Observe the PDP.

1. Navigate to the PDP. User is on PDP

2. Observe the product images section.

1. Navigate to the PDP. User is on PDP

2. Check for available variants like size/colour
etc options.

1. Compare the product details on the PDP Log into Magento Backend
with those displayed on the Magento
Backend
1. Click on a product with incomplete details. User is on PLP
2. Observe the PDP.

1. Navigate to the PDP. User is on PDP

2. Scroll to the More Information section.

1. Navigate to the PDP. User is on PDP

2. Look for social media sharing icons.

1. Select Variants user is in pdp

2. Enter quantity.
3. Click "Add to Cart".

1. Click "Add to Cart" without selecting size or user is in pdp

colour

1. Select size/colour that is known to be out user is in pdp

of stock.
2. Click "Add to Cart".

1.. Select valid size/colour. user is in pdp

2. Click "Add to Cart". twice
3. Check the cart icon count.

1. Select size/colour. user is in pdp

2. Click "Add to Cart" without enough stock.
3. Check the selections after the error.

1. Select size/colour. user is in pdp

2. Enter a quantity greater than 1.
3. Click "Add to Cart".

1. Log out and then log back in. user is in pdp

2. Check the cart for added items.
1. Add a product to the cart. user is in pdp
2. Observe the confirmation message
duration.

1. As a guest, attempt to add a product to the user is in pdp

cart.
2. Log in and repeat the process.

1. Select size/colour. user is in pdp

2. Enter a very large quantity (e.g.,
1000000).
3. Click "Add to Cart".

1. Scroll to the reviews section on the PDP. user is on pdp

1. Scroll to the reviews section on the PDP. user is on pdp

1. Scroll to the reviews section. user is on pdp with product having

2. Select a filter (e.g., most recent, highest multiple reviews
rating).

1. Scroll to the reviews section. user is on pdp with product having

2. Select the "most recent" filter. multiple reviews

1. Scroll to the reviews section. user is on pdp with product having

2. Select the "highest rating" filter. multiple reviews

1. Scroll to the reviews section. user is on pdp with product having

multiple reviews

1. Scroll to the reviews section. user is on pdp with product having

multiple reviews
1. Scroll to the reviews section. user is on pdp with product having
multiple reviews

1. Scroll to the reviews section. user is on pdp with product having

multiple reviews

1. Logon as admin
2, marketing > All reviews

1. Logon as admin
2, marketing > All reviews

1. Logon as admin
2, marketing > All reviews

1. Logon as admin
2, marketing > All reviews
 Medium Low
23 4

Test Device (for

Expected Results Test Data
mobile)

The PDP displays product name,

description, price, discounts, available
sizes/ variants, colours, and images,
quantity text box, more information, NA Desktop
reviews, Wishlist icon, add to cart button

The user is redirected to the correct PDP

URL for the selected product.
NA Desktop

In the PDP,a message should be there

indicating "This product is currently out of
stock." NA Desktop

All product images are displayed correctly,

allowing for zoom or enlargement options.
NA Desktop

Available variants sizes,colors etc are

displayed as selectable options on the PDP.
NA Desktop

The product name, description, price, and

options match between the Magento
Backend and PDP
NA Desktop
An error message states "Product details
are currently unavailable."
NA Desktop

Detailed product specifications are

displayed, providing comprehensive
information about the product in the More NA Desktop
information tab section

Social media sharing options (e.g.,

Facebook, Twitter) are available and
functional. NA Desktop

The product is added to the cart, and a

confirmation message is displayed.
NA Desktop

An error message states, "Please select

size and colour before adding to the cart."
NA Desktop

The message indicates, "Selected variant

is not available."
NA Desktop

The cart icon reflects the updated count of

items in the cart.; here the count shows 2.
NA Desktop
NOTE: test with different counts

The selected size and colour remain

selected, allowing the user to retry adding
the product. NA Desktop

The cart reflects the correct quantity of the

selected product added.
NA Desktop

The previously added items are still

present in the cart after logging back in.
NA Desktop
The confirmation message displays for a
defined period (e.g., 2 or 3 seconds) before
disappearing. NA Desktop

The guest user is prompted to log in or

register before adding the product, while
the logged-in user adds successfully.
NA Desktop

The system handles the input correctly,

either adding the product or displaying an
error if the limit is exceeded.
NA Desktop

Customer reviews and ratings are

displayed for the product.
NA Desktop

A message stating "No reviews available

for this product" is displayed in the reviews
section. NA Desktop

The reviews are displayed according to the

selected filter, showing the relevant
reviews at the top. NA Desktop

The reviews are displayed starting from the

most recently submitted reviews.
NA Desktop

the reviews are displayed starting from the

highest-rated reviews.
NA Desktop

Each review displays the reviewer's name,

rating, and review content correctly.
NA Desktop

The reviews are displayed in pages, with

pagination controls to navigate through
them. NA Desktop
Each review displays the corresponding
user rating (e.g., stars or numerical rating)
next to the review. NA Desktop

Verify that responses from the seller to

reviews are visible if applicable.
NA Desktop

In Magento admin can view tall he posted

reviews NA Desktop

All newly posted reviews by user should be

in pending status
NA Desktop

when admin approves review; the review

should be shown on the front end Utec
marketplace
cross verify the same on front end for the NA Desktop
respective product

when admin selects not approved review;

the review should not be shown on the
front end Utec marketplace
cross verify the same on front end for the NA Desktop
respective product
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

High

Low

Medium

Medium

Medium

High
Medium

Medium

Medium

Medium

Medium

Medium

Medium

Medium

Medium

High
 Low

Medium

Medium

Low

Medium

Medium

Medium

Medium

High
 Low

Medium

Medium

Medium

Medium

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_CM_001 MC-54 Verify add items to

cart
Integration

UT_CM_002 MC-54 Verify remove items

Integration from cart

UT_CM_003 MC-54 Verify adding and

MC-205 removing items
Integration multiple times

UT_CM_004 MC-54 Verify updating item

quantity scenario
Integration

UT_CM_005 MC-54 Verify when buyer

MC-205 adds items above
stock availability
Integration

UT_CM_006 MC-54 Verify remove all

Integration MC-204 items from cart
UT_CM_007 MC-54 Verify if Managing
Multiple Carts is
available

Integration

UT_CM_008 MC-204 Verify the items

displayed in cart

Integration

UT_CM_009 MC-206 Verify that the pin

code cannot be
changed from the cart
Integration to the "Thank You"
page.

UT_CM_010 MC-206 Verify that an error

message is displayed
when the user tries to
Integration change the pin code
on the cart page.

UT_CM_011 MC-206 Verify that the system

prompts the user to
select an address with
Integration the same pin code
during checkout.

UT_CM_012 MC-207 Verify that products

from selected sellers
Integration can be added to the
cart.
UT_CM_013 MC-207 Verify that products
from multiple sellers
Integration can be added to the
cart.

UT_CM_014 MC-207 Verify that an error

message is displayed
when trying to add
products from a seller
Integration not available for the
region.

UT_CM_015 MC-208 Verify that estimated

delivery dates and
shipping charges are
Integration displayed for each
product in the cart.

UT_CM_016 MC-208 Verify if buyer can

modify the delivery
Integration date

UT_CM_017 MC-208 Verify that estimated

delivery dates and
shipping charges are
correctly displayed for
Integration multiple products.

UT_CM_018 MC-208 Verify that the

estimated delivery
dates are displayed as
Integration per UI/UX format.

UT_CM_019 MC-208 Verify that the system

shows multiple
shipments during
Integration checkout without
additional shipping
charges.

UT_CM_020 MC-208 Verify that shipping

charges are correctly
calculated based on
Integration product weight and
delivery options.
UT_CM_021 MC-209 Verify that the "Add to
RFQ" button is
displayed when the
Integration cart value exceeds
the defined threshold

UT_CM_022 MC-209 Verify that the user

can successfully add
the cart to the RFQ list
Integration when the button is
displayed.

UT_CM_023 MC-209 Verify that the "Add to

RFQ" button is not
displayed when the
Integration cart value is below the
defined threshold.

UT_CM_024 MC-209 Verify that the "Add to

RFQ" button visibility
updates when the cart
Integration value changes relative
to the threshold.

UT_CM_025 MC-209 Verify the behaviour

when the cart value is
Integration exactly at the
threshold.
 Total No. Of Test Cases : 25
High
Complexity Count :
1
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Browse the product catalogue. Logged in as a buyer

2. Select an item.
3. Click "Add to Cart".

1. View items in the cart. Logged in as a buyer

2. Click the "X" button next to an item.

1. Add an item to the cart. Logged in as a buyer

2. Remove an item from the cart.
3. View the cart again.

1. View items in my cart. Buyer is in cart page

2. Increase the quantity of an item.

1. Login to Magento and for the item's SKU Buyer is in cart page
verify the stock
2. In Utec Marketplace, Add an item in my
cart.
2. Increase the quantity beyond available
stock.
1. View items in my cart. Buyer is in cart page
2. Click "Remove All" or similar.
1. Navigate to the cart section of the User is logged into the application.
application. User has access to multiple cart
2. Identify and select the "Buy Now Cart." features (e.g., Buy Now Cart and RFQ
3. Add multiple items to the "Buy Now Cart." Cart).
4. Save the current state of the "Buy Now
Cart."
5. Switch to the "RFQ Cart."
6. Add different items to the "RFQ Cart."
7. Save the current state of the "RFQ Cart."
8. Switch back to the "Buy Now Cart."
9. Verify the items in the "Buy Now Cart."
10. Switch back to the "RFQ Cart."
11. Verify the items in the "RFQ Cart."

1. Navigate to the homepage or product Logged in as a buyer

listing page.
2. Add multiple products to the cart.
3. Click on the cart icon.

1. Add items to the cart. Buyer is in cart page

2. Proceed to the checkout page.

1. Add items to the cart. Buyer is in cart page

2. Attempt to change the pin code on the cart
page.
3. Try to proceed.

1. Add items to the cart. Buyer is in cart page

2. Proceed to checkout.
3. Select a different shipping address with a
different pin code.

1. Navigate to the Product Detail Page (PDP). Buyer is in cart page

2. Choose a seller.
3. Add the product to the cart.
1. Navigate to the Product Detail Page (PDP). Buyer is in cart page
2. Add the product to the cart.
3. Repeat for different sellers.

1. Navigate to the PDP. Buyer is in cart page

2. Choose a seller that is not available for the
user’s region.
3. add the product to the cart

1. Add products to the cart. Buyer is in cart page

2. Navigate to the cart page.

1. Add products to the cart. Buyer is in cart page

2. Navigate to the cart page.
3. validate if buyer can change delivery date

1. Log in to the application. buy has added products from

2. Add products from at least two different different sellers to the cart.
sellers to the cart.
3. Click on the cart icon to view the cart
page.

1. Log in to the application. Buyer is in cart page

2. Add multiple products to the cart.
3. Click on the cart icon to view the cart
page.
4. Observe the format of the estimated
delivery dates displayed.
1. Add products from a seller that offers Buyer is in cart page
partial or multiple deliveries.
2. Proceed to checkout.

1. Log in to the application. buyer has added products of varying

2. Add products of different weights to the weights to the cart.
cart.
3. Click on the cart icon to view the cart
page.
4. Check the displayed shipping charges for
accuracy.
1. Log in to the application. User has added products to the cart,
2. Add products to the cart until the total exceeding the predefined threshold.
exceeds the defined threshold.
3. Click on the cart icon to view the cart
page.

1. Log in to the application. cart value exceeds the predefined

2. Add products to the cart to exceed the threshold.
threshold.
3. Click on the cart icon.
4. Click the "Add to RFQ" button.
5. Confirm the RFQ submission.

1. Log in to the application. buyer has added products to the cart,

2. Add products to the cart to keep the total keeping the total below the threshold.
below the defined threshold.
3. Click on the cart icon to view the cart
page.

1. Log in to the application. User adds and removes products from

2. Add products to exceed the threshold. the cart.
3. Verify the "Add to RFQ" button is visible.
4. Remove products to drop below the
threshold.
5. Check again.

1. Log in to the application. cart value is set exactly at the

2. Add products to the cart to exactly meet predefined threshold
the threshold.
3. Click on the cart icon to view the cart
page.
 Medium Low
16 8

Test Device (for

Expected Results Test Data
mobile)

The item is added to my cart with updated

NA Desktop
details (quantity & price).

The item is removed, and the cart total is

NA Desktop
recalculated.

The subtotal, taxes, and discounts should

NA Desktop
be recalculated and displayed.

The cart updates with the new quantity and

NA Desktop
recalculated total.

An error message displays: "Quantity

exceeds available stock.
NA Desktop

The cart displays "Your cart is empty." NA Desktop

The system should allow switching
between the "Buy Now Cart" and "RFQ
Cart" without errors.
Items added to the "Buy Now Cart" should
remain unchanged when switching to the
"RFQ Cart."
Items added to the "RFQ Cart" should
remain unchanged when switching back to
the "Buy Now Cart." NA Desktop
The saved state of each cart should reflect
the correct items when switching between
them.

NOTE: Both carts retain their respective

items without any overlap or loss of data.

A summary of the cart is displayed,

including:
•Product names
•Product images
•Prices of each product
•Quantity of each product
•Seller information for each product NA Desktop
•Any applicable discounts
The total cart value is correctly calculated
and displayed. The number of SKUs
(unique products) in the cart is displayed.

The pin code selected on the home page is

retained, and the user cannot change it on
the checkout page.
NA Desktop

An error message is displayed stating, "Pin

code change is not allowed at this stage."

NA Desktop

The system prompts the user to select an

address with the same pin code as initially
chosen.
NA Desktop

The product from the selected seller is

added to the cart, and the cart can include
products from multiple sellers. NA Desktop
The product from the selected seller is
added to the cart, and the cart can include
products from multiple sellers. NA Desktop

An error message is displayed stating,

"Seller not available for this region."

NA Desktop

Estimated delivery dates and shipping

charges are displayed for each product in
the cart
NA Desktop

NA Desktop

Each product displays its own estimated

delivery date and shipping charge,
accurately reflecting the respective seller's
shipping policies.
NA Desktop

Estimated delivery dates are displayed in a

clear format (e.g., "Expected delivery by
October 25, 2024").
NA Desktop

The system indicates that delivery will be

split into multiple shipments, and no
additional shipping charge is applied to the
buyer. NA Desktop

Shipping charges are displayed correctly

for each product based on weight and
seller policies.
NA Desktop
The "Add to RFQ" button is displayed on
the cart page.
NA Desktop

The cart is successfully added to the RFQ

list, and the user receives a confirmation
message. A notification appears stating,
"Your cart total must exceed the threshold NA Desktop
to add to RFQ."

The "Add to RFQ" button is not displayed

on the cart page.

NA Desktop

The "Add to RFQ" button is displayed when

the cart exceeds the threshold and hidden
when it falls below.
NA Desktop

The "Add to RFQ" button is displayed,

allowing the user to add the cart to the
RFQ list. NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Medium

Medium

Medium

Low
Medium

Low

Medium

Medium

High

Medium
Medium

Medium

Medium

Low

Low

Low

Medium

Medium
 Low

Medium

Low

Medium

Low
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_CO_001 Integration Verify that the user

can successfully
select and complete a
purchase using a
MC-216 credit card.

UT_CO_002 Integration Verify that the user

can successfully
select and complete a
MC-216 purchase using UPI

UT_CO_003 Integration Verify that the user

can select and
complete a purchase
MC-216 using a bank transfer.

UT_CO_004 Integration Verify that the system

correctly handles
invalid payment
information during
MC-216 checkout.

UT_CO_005 Integration Verify the buyer

selects a payment
option that is
MC-216 unavailable (e.g.,
service outage),
UT_CO_006 Integration Verify that the user
can apply a
promotional code
MC-216 before selecting a
payment option.

UT_CO_007 Integration Verify that the

selected payment
option is retained if
MC-216 the user navigates
back to the payment
page.

UT_CO_008 Integration Verify that the admin

can configure the
advance payment
MC-216 amount based on cart
amounts.

UT_CO_009 Integration Verify that the user

can complete a
purchase using the
online advance
MC-216 payment method.

UT_CO_010 Integration Verify that advance

payment options are
not displayed for cart
MC-216 amounts below
500,000.

UT_CO_011 Integration Verify that advance

payment options are
not displayed for cart
MC-216 amounts below
500,000.

UT_CO_012 Integration Verify that the system

handles cases where
an online advance
MC-216 payment fails.
UT_CO_013 Integration Verify if all delivery
mode options (BOPIS,
ROPIS, Home
MC-218 Delivery) are available
on the checkout
screen.

UT_CO_014 Integration Validate if a default

delivery mode is
selected when the
MC-218 buyer is on the
checkout screen.

UT_CO_015 Integration Verify that buyer can

change their selected
delivery mode before
MC-218 completing the
checkout process.

UT_CO_016 Integration Verify when buyer

selects a delivery
mode unavailable for
MC-218 their region, error
message is displayed

UT_CO_017 Integration Verify if the system

calculates taxes
correctly based on the
MC-219 product type.

UT_CO_018 Integration Verify if the system

calculates taxes
MC-219 correctly based on the
shipping location

UT_CO_019 Integration Verify when invalid

address is given, if
system displays error
MC-219

UT_CO_020 Integration Verify if tax

calculations are
consistent across
MC-219 different devices and
browsers.
UT_CO_021 Integration Verify for buyer, if
detailed order
summary is displayed
MC-220 at checkout

UT_CO_022 Integration Verify if appropriate

error message is
displayed when
MC-220 shipping charges are
not calculated

UT_CO_023 Integration Verify if appropriate

error message is
displayed when a
MC-220 product is Out of
Stock

UT_CO_024 Integration Verify if the order

summary displays
MC-220 correctly on different
devices

UT_CO_025 Integration Verify if system

securely processes
the payment through
MC-221 the integrated
payment gateway,

UT_CO_026 Integration Verify if buyer can

switch between
MC-221 payment options
without issues.

UT_CO_027 Integration Verify if appropriate

error messages are
MC-221 displayed for invalid
payment details

UT_CO_028 Integration Verify if appropriate

error messages are
displayed when
MC-221 Payment Gateway is
down
UT_CO_029 Integration Verify that the
payment processing
page is responsive
MC-221 across different
devices.

UT_CO_030 Integration Verify when order is

placed & payment is
MC-222 done if thank you
page is displayed

UT_CO_031 Integration Verify when order is

placed & payment is
failed if thank you
MC-222 page is not displayed
 Total No. Of Test Cases : 31
High
Complexity Count :
30
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Navigate to the shopping cart. User is logged in and has items in the
2. Click on "Proceed to Checkout." shopping cart.
3. Select "Credit Card" as the payment
option.
4. Fill in the credit card details (Card Number,
Expiration Date, CVV).
5. Click "Place Order."

1. Navigate to the shopping cart. User is logged in and has items in the
2. Click on "Proceed to Checkout." shopping cart.
3. Select "UPI" as the payment option.
4. Fill in the UPI details
5. Click "Place Order."

1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart.
2. Select "Bank Transfer" as the payment
option.
3. Review the bank transfer instructions and
confirm the order.

1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart.
2. Select "Credit Card" as the payment
option.
3. Enter invalid credit card details (e.g.,
wrong card number).
4. Click "Place Order."

1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart.
2. Enter a valid promotional code.
3. Select a payment option (e.g., Credit Card,
UPI).
4. Click "Place Order."
1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart.
2. Enter a valid promotional code.
3. Select a payment option (e.g., Credit Card,
UPI).
4. Click "Place Order."

1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart.
2.Select a payment option (e.g., UPI).
3. Navigate back to the previous page and
then return to the payment page.

1. Navigate to System > Configuration > User is logged in as an admin.

Payment Methods.
2. Locate the advance payment settings. NOTE: The customer should be
3. Enter advance payment amounts for cart opting for ROPIS only
value >500,000
4. Save the configuration.
1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart exceeding 500,000.
2. Select the advance payment option.
3. Choose an online payment method NOTE: The customer should be
4. Complete the payment process. opting for ROPIS only

Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart totalling 200,000.

Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart totalling 499999.

1. Navigate to the shopping cart and click User is logged in and has items in the
"Proceed to Checkout." shopping cart exceeding 500000.
2. Select the advance payment option and
choose an online payment method.
3. Enter invalid payment details to trigger a
failure.
1. Navigate to the checkout screen. the buyer is on the checkout page
2. Validate the delivery mode options given
3. select a delivery mode (BOPIS, ROPIS, or
Home Delivery),

1. Navigate to the checkout screen. the buyer is on the checkout page

2. Validate the delivery mode options given

1. Change the selected delivery mode to the buyer is on the checkout page
another option.
2. Complete the checkout process.

1. Enter an incomplete or invalid address. the buyer is on the checkout page

2. Attempt to complete the checkout process.

1. Add products of different types e.g., Buyer is on the checkout page,

taxable, non-taxable, sale products to the
cart.
2. Proceed to the checkout page.

1. Change the shipping address to a different Buyer is on the checkout page,

location (e.g., different state or region with
different tax rates).
2. Proceed to the checkout page.

1. Enter invalid or missing address in the Buyer is on the checkout page,

shipping address
2. Proceed to the checkout page.

1. Access the UltraTech marketplace on Buyer is on the checkout page,

different devices (desktop, mobiles).
2. Complete the checkout process on each
device.
1. Navigate to the shopping cart Buyer is on the checkout page,
2. View the order summary

Navigate to the shopping cart and click Buyer is on the checkout page,
"Proceed to Checkout."

Navigate to the shopping cart and click Buyer is on the checkout page, and a
"Proceed to Checkout." product should be Out of Stock

Access the UltraTech marketplace checkout Buyer is on the checkout page,

page on various devices.

Navigate to the shopping cart and click Buyer is on the checkout page,
"Proceed to Checkout."
2. Proceed to the payment section of the
checkout process.

1. Select a payment option e.g., UPI. Buyer is on the checkout page,

2. Change the payment option to credit card
or net banking.

1. Enter invalid payment details for any Buyer is on the checkout page,
payment option like incorrect card number,
expired UPI ID
2. Attempt to submit the payment.

1. Enter invalid payment details for any Buyer is on the checkout page,
payment option like incorrect card number,
expired UPI ID
2. Attempt to submit the payment.
Access the UltraTech marketplace checkout Buyer is on the checkout page,
page on various devices desktop, tablet,
mobile.

Place an order with successful payment Buyer is on payment page of the

order

Place an order with unsuccessful payment Buyer is on payment page of the

order
 Medium Low
0 0

Test Device (for

Expected Results Test Data
mobile)

The order should be processed

successfully, and a confirmation message
should be displayed, along with the order
summary.
NA Desktop

The order should be processed

successfully, and a confirmation message
should be displayed, along with the order
summary. NA Desktop

The order should be processed

successfully, and a confirmation message
should be displayed, along with the order
summary. NA Desktop

An error message should be displayed

indicating that the payment details are
invalid, and the order should not be
processed.
NA Desktop

An error message should be displayed

stating, "Payment option temporarily
unavailable. Please choose another
method." NA Desktop
The promotional discount should be
applied, and the order should be processed
successfully with the updated total.
NA Desktop

The previously selected payment option

should be still displayed.

NA Desktop

The advance payment should be saved

successfully, and the values should be
displayed correctly in the configuration.
NA Desktop

The order should be processed

successfully, and a confirmation message
should be displayed, along with the order
summary.
NA Desktop
A confirmation email should be sent/
received, regarding the advance payment
made.

Advance payment options should not be

displayed during checkout.
NA Desktop

Advance payment options should not be

displayed during checkout.
NA Desktop

An error message should be displayed

indicating the payment failure, and the
order should not be processed.
NA Desktop
The options for BOPIS, ROPIS, and Home
Delivery are all visible and selectable. The
system should apply the selected mode
and the order summary should get updated NA Desktop
with the corresponding delivery details.

Radio button option should be available for

the selection and one option should be
selected
NA Desktop

The checkout process should reflect the

new delivery mode selection accurately in
the order confirmation.
NA Desktop

The system should display an error

message stating, "Delivery mode not
available for your selected location."
NA Desktop

The system should automatically calculate

the applicable taxes based on the location
and product type and the total order
amount, including tax, should be displayed NA Desktop
in the order summary.

The tax amount should be automatically

calculated on the new shipping address.
NA Desktop

The system should display an error

message stating, "Unable to calculate tax
due to missing address information." and
the checkout process should not proceed NA Desktop
until the issue is resolved.

The tax calculation should be consistent

across all devices and browsers.
NA Desktop
The summary should display the product
details, shipping charges, and any
applicable discounts and the buyer should
be able review the total order amount NA Desktop
before proceeding.

An error message should be displayed

stating, "Unable to calculate shipping
charges. Please try again."
NA Desktop

An error message should be displayed, and

should not allow buyer to proceed to
checkout until the issue is resolved.
NA Desktop

The order summary should be fully visible

and properly formatted on all devices,
maintaining readability and usability. NA Desktop

The system securely processes the

payment through the integrated payment
gateway and the buyer is redirected to the
"Thank You" page after a successful NA Desktop
transaction.

The payment process should update

correctly without losing the cart
information, and the customer should be NA Desktop
able to proceed with the new payment
option.
An error message is displayed stating,
"Payment processing failed. Please try
again later or use another payment NA Desktop
method."

An error message is displayed stating,

"Payment processing failed. Please try
again later or use another payment
method." NA Desktop
The payment processing options and
layout should be properly formatted and
functional on all devices.
NA Desktop

The system displays a "Thank You" page

with the order confirmation details and the
buyer receives a confirmation email with NA Desktop
the order summary.

the system displays an error message

stating, "Order placement failed. Please try
again."
NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

High

High

High

High

High
High

High

High

High

High

High

High
High

High

High

High

High

High

High

High
High

High

High

High

High

High

High
High

High

High
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_SC_001 Integration Verify if sellers can

access the onboarding
page & input field for
MC-125 minimum cart amount
is available

UT_SC_002 Integration Verify if the system

accepts valid input for
the minimum cart
MC-125 amount.

UT_SC_003 Integration Verify if appropriate

error messages are
MC-125 displayed for invalid
inputs.

UT_SC_004 Integration Verify if the system

has a maximum cart
MC-125 amount.

UT_SC_005 Integration Verify if sellers can

successfully submit
the minimum cart
MC-125 amount

UT_SC_006 Integration Verify if the

onboarding page is
MC-125 user-friendly.

UT_SC_007 Integration Verify if the sellers

MC-125 can enable free
shipping.
 UT_SC_008 Integration Verify if seller can set
a minimum cart value
MC-125 for free shipping.

UT_SC_009 Integration Verify id seller can set

a maximum limit for
MC-125 the free shipping
threshold.

UT_SC_010 Integration Verify if check is done

when cart value is
below the free
MC-125 shipping threshold
during checkout.

UT_SC_011 Integration Verify if Free Shipping

is available for Orders
MC-125 Above a Certain Cart
Value

UT_SC_012 Integration Verify if seller can

changes to the free
shipping threshold
MC-125 and apply them

UT_SC_013 Integration Verify if Shipping

Charges are
Calculated Using Per-
Kilometre Rates
MC-125

UT_SC_014 Integration Verify if Flat Rate

Applied to All Pin
MC-125 Codes

UT_SC_015 Integration Verify if Pin Code-

Specific Rates are
Applied
MC-125

) UT_SC_016 Integration Verify shipping

charges calculation
MC-124 for valid pin code
UT_SC_017 Integration Verify if vehicle type
selection can be done
MC-124 based on weight

UT_SC_018 Integration Verify if shipping

charges for different
MC-124 weight categories

UT_SC_019 Integration Verify if invalid pin

code is entered error
MC-124 message is displayed

UT_SC_020 Unit Validate per-kilometre

rate application and
distance calculation to
MC-124 delivery pin code

UT_SC_021 Integration Verify if shipping

charge updates for
changing cart weight
MC-124

UT_SC_022 Integration Verify shipping

charges recalculation
on addition or
MC-124 deletion of item

UT_SC_023 Integration Verify shipping

charges for maximum
MC-124 weight capacity

UT_SC_024 Integration
Verify if shipping
charge decrease when
MC-124
weight is reduced

UT_SC_025 Integration Verify if shipping

charges remain
MC-124 unchanged for no
weight change
UT_SC_026 Integration Verify if system
performance is stable
during multiple cart
MC-124 updates

UT_SC_027 Integration Verify if error

message is displayed
for overweight vehicle
MC-124 type

UT_SC_028 Integration Verify if contact

prompt for support
MC-124 message is displayed
for buyer

UT_SC_029 Integration Verify if error

message is displayed
with different vehicle
MC-124 types

UT_SC_030 Integration Verify the system

behaviour for a valid
MC-124 vehicle type after
error

UT_SC_031 Integration Verify if the type of

error message for
MC-124 edge case (exact
capacity)

UT_SC_032 Integration Verify if system

prompts for vehicle
MC-126 number input when
updating status

UT_SC_033 Integration Verify if system

prompts for driver’s
MC-126 name input when
updating status

UT_SC_034 Integration Verify if system

prompts for AWB
number input when
MC-126 updating status
UT_SC_035 Integration Verify if seller can
take printout of the
MC-126 invoice

UT_SC_036 Integration Verify if buyer is

notified of order
status and shipping
MC-126 details

UT_SC_037 Integration Verify if seller can

update order status to
MC-126 "Completed"

UT_SC_038 Integration Verify prompt for

Proof of Delivery
MC-126 (POD) input

UT_SC_039 Integration Verify if buyer is

notified after status
MC-126 update

UT_SC_040 Integration Verify system

behaviour with invalid
MC-126 POD

UT_SC_041 Integration Verify system

functionality with
MC-126 missing POD

UT_SC_042 Integration Verify if RMA is

triggered for incorrect
MC-127 shipping charge

UT_SC_043 Integration Verify recalculation of

shipping charge
MC-127

UT_SC_044 Integration Verify system

behaviour for valid
MC-127 shipping charge
UT_SC_045 Integration Verify RMA process
handles multiple
MC-127 discrepancies

UT_SC_046 Integration Verify refund is

processed for
MC-127 overcharged shipping

UT_SC_047 Integration Verify notification to

buyer about RMA
MC-128 process

UT_SC_048 Integration Verify notification to

seller about RMA
MC-128 process

UT_SC_049 Integration Verify if system sends

a final notification to
both the buyer and
MC-128 the seller
 Total No. Of Test Cases : 49
High
Complexity Count :
45
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Log in to the seller account. seller is on the onboarding page.

2. Navigate to the onboarding section.
3. validate the field for entering the minimum
cart amount.

1. Enter a valid numerical value (e.g., 500) seller is on the onboarding page.
into the minimum cart amount field.
2. Click on Submit

1. Enter invalid values (e.g., negative seller is on the onboarding page.

numbers, letters, special characters) into the
minimum cart amount field.
2. Click on Submit

1. Enter a value exceeding the maximum seller is on the onboarding page.

limit e.g., 10000000
2. Click on Submit

1. The seller has entered all mandatory fields seller is on the onboarding page.
and valid value in minimum cart amount.
2. Click on Save
3. Logout & Login back to the onboarding
section

Validate the layout, design, and usability of seller is on the onboarding page.
the input field and surrounding elements

Validate if seller can enable and disable free Seller is logged in and is in setting
shipping section
1. Input a valid value e.g., 1000 in the free seller has enabled the free shipping
shipping threshold field. option
2. Save the changes

1. Input a large/maximum value e.g., 20000 seller has enabled the free shipping
in the free shipping threshold field. option
2. Save the changes

1. Login as a buyer and add few products to The seller has set a free shipping
the cart; making sure the cart total is below threshold.
the free shipping threshold

1. Login as a buyer and add few products to The seller has set a free shipping
the cart; making sure the cart total is below threshold.
the free shipping threshold

1. Change the free shipping threshold to a The seller has previously set a free
new value i.e. from 750 to 1000 shipping threshold.
2. Save the changes
3. Login as a buyer and add few products to
the cart; making sure the cart total value is
near the older set threshold

1. Login as a buyer and add few products to During onboarding seller has set
the cart. 1. per-kilometre rates for each vehicle
type;
2. seller's location is defined by the
primary pin code

1. Login as a buyer and add few products to seller has chosen a flat rate for all pin
the cart. codes during onboarding

1. Login as a buyer and add few products to seller has opted for pin code-specific
the cart and enters a pin code(560085) rates during onboarding(560132)

Enter a valid delivery pin code Buyer has items in the cart with a
combined weight.
Enter a valid delivery pin code Buyer has items in the cart with
known weight.

1. Add items of varying weights to the cart. Buyer has items in different weight
2. Enter a valid delivery pin code. categories.

Enter an invalid delivery pin code. Buyer has items in the cart.

Enter an valid delivery pin code. Buyer has items in the cart with
known weight.

1. Enter a valid delivery pin code. Buyer has items in the cart.
2. Change the items in the cart to alter total
weight.

1. Add 2 items to the cart. Buyer has items in the cart with a
2. Enter a valid delivery pin code. combined weight.
3. Remove an item from the cart.

Add additional item such that exceeds the Buyer has items close to the
maximum weight limit in cart maximum weight limit

1. Remove an item that reduces the total cart Buyer has items in the cart with a
weight. known weight.
2. Enter a valid delivery pin code.

1. Add and then remove the same item, Buyer has items in the cart with a
maintaining total weight. known weight.
2. Enter a valid pin code.
1. Rapidly add and remove multiple items Buyer has items in the cart with a
from the cart. known weight.
2. Enter a valid delivery pin code.

1. . Add items to the cart. Buyer has a cart with combined

2. Select a vehicle type with insufficient weight > vehicle capacity
capacity.
3. validate if shipping charge is shown

1. . Add items to the cart. Buyer has a cart with combined

2. Select a vehicle type with insufficient weight > vehicle capacity
capacity.
3. validate if shipping charge is shown

1. . Add items to the cart. Buyer has a cart with combined

2. Select a vehicle type with insufficient weight > vehicle capacity
capacity.
3. validate if shipping charge is shown

1. . Add items to the cart. Buyer has a cart with combined

2. Select a vehicle type with insufficient weight < vehicle capacity
capacity.
3. validate if shipping charge is shown

1. . Add items to the cart. Buyer has a cart with combined

2. Select a vehicle type with insufficient weight = vehicle capacity
capacity.
3. validate if shipping charge is shown

1. Log in as a seller. Seller has an order ready for dispatch

2. Select the order.
3. Update the status to "Out for Delivery".

1. Log in as a seller. Seller has an order ready for dispatch

2. Select the order.
3. Update the status to "Out for Delivery".

1. Log in as a seller. Seller has an order ready for dispatch

2. Select the order.
3. Update the status to "Out for Delivery".
4. Input vehicle number.
5. Input driver’s name.
1. Log in as a seller. Seller has an order ready for dispatch
2. Select the order.
3. Update the status to "Out for Delivery".
4. Add the AWB number.

1. Log in as a seller. Seller has an order ready for dispatch

2. Select the order.
3. Update the status to "Out for Delivery".
4. Add the AWB number.
5. Confirm updates.

1. Log in as a seller. Seller has delivered the order to the

2. Select the order. buyer
3. Update the order status to "Completed".

1. Log in as a seller. Seller has delivered the order to the

2. Select the order. buyer
3. Update the order status to "Completed".

1. Log in as a seller. Seller has delivered the order to the

2. Select the order. buyer
3. Update the order status to "Completed".
4. Enter the POD delivery code.

1. Log in as a seller. Seller has delivered the order

2. Select the order.
3. Update the order status to "Completed".
4. Enter an invalid POD.

1. Log in as a seller. Seller has delivered the order

2. Select the order.
3. Update the order status to "Completed".
4. Leave POD blank.

1. Log in as a buyer. Buyer has a cart with a shipping

2. Add items to the cart. charge mismatch
3. Proceed to checkout with a mismatched
shipping charge.

1. Log in as a buyer. Buyer has a cart with a shipping

2. Add items to the cart. charge mismatch
3. Proceed to checkout with a mismatched
shipping charge.

1. Log in as a buyer. Buyer has a cart with a correct

2. Add items to the cart. shipping charge
3. Proceed to checkout with a correct
shipping charge.
1. Log in as a buyer. Buyer has multiple items with varying
2. Add items to the cart with different charges
discrepancies.
3. Proceed to checkout.

1. Log in as a buyer. System identifies an overcharged

2. Complete a purchase with an overcharged shipping fee
shipping amount.
3. RMA process is triggered.

1. Log in as a buyer. Buyer has a cart with a shipping

2. Add items to the cart. charge mismatch
3. Proceed to checkout with a mismatched
shipping charge.

1. Log in as a buyer. Buyer has a cart with a shipping

2. Add items to the cart. charge mismatch
3. Proceed to checkout with a mismatched
shipping charge.

As Admin Check email notification for buyer Return of the merchandise is

and seller RMA is sent. authorized
 Medium Low
4 0

Test Device (for

Expected Results Test Data
mobile)

The onboarding page should load

successfully, an input field should be
present for sellers to input the minimum
cart amount for free delivery. NA Desktop
The field should display a default value

The system should accept the value

without errors and should allow the seller
to proceed.
NA Desktop

The system should display an error

message indicating the input is invalid.
NA Desktop

The system should display an error

message indicating that the amount
exceeds the maximum limit. NA Desktop

The previously entered minimum cart

amount should be displayed correctly in
the input field+H26.
NA Desktop

The interface should be intuitive, easy to

navigate, and visually appealing
NA Desktop

The seller should see an option to opt for

free shipping NA Desktop
The system should accept the value
without errors and confirm that the
threshold has been se NA Desktop

The system should display an error

message indicating the amount exceeds
the maximum limit. NA Desktop

The system should notify the buyer that

the cart total does not qualify for free
shipping.
The system should display a message NA Desktop
indicating how much more the buyer needs
to spend to qualify for free shipping

the system should automatically apply

free shipping to the order, regardless of
the delivery pin code or cart weight. NA Desktop

The system should enforce the new

threshold and respond accordingly during
checkout.
NA Desktop

The system calculates the shipping charge

based on the distance from the seller’s
primary pin code to the buyer’s delivery
pin code
and NA Desktop
the system multiplies the per-kilometre
rate by both the distance and the total
weight of the buyer’s cart.

The system should apply the flat rate as

the shipping charge, regardless of the
buyer's delivery location and cart weight. NA Desktop

The system should apply the rate specific

to that pin code and vehicle type, adjusting
the shipping charges based on both the
delivery location and the weight of the NA Desktop
cart.

System should calculate shipping charges

based on the vehicle type and distance.
NA Desktop
System should allocate the correct vehicle
type based on the total cart weight.
NA Desktop

System should calculate shipping charges

correctly for each weight category.
NA Desktop

System should display an error message

indicating the pin code is invalid.
NA Desktop

The system should calculate the shipping

charge using the per-kilometre rate set by
the seller for that vehicle type and the
distance to the delivery pin code. NA Desktop

System should display calculated shipping

charges clearly on the checkout page.
System should recalculate and update
shipping charges based on new cart NA Desktop
weight.

System should recalculate shipping

charges based on the updated cart weight
and displays the new charges.
NA Desktop
Shipping charges should update in real-
time without needing to refresh the page.

System should display an error or message

indicating that the maximum weight
capacity for shipping has been reached. NA Desktop

System should recalculate and display

decreased shipping charges based on the
new weight. NA Desktop

System should show that shipping charges

remain unchanged.
NA Desktop
System should handle the changes without
lag or errors, recalculating charges
accurately.
Shipping charge display should be NA Desktop
consistent with the cart weight and vehicle
type after each update.

System should display an error message:

"Shipping charge cannot be calculated due
to capacity issue."
NA Desktop

System should prompt: "Please contact our

support team for assistance in resolving
the issue." NA Desktop

System should display an error message:

"Shipping charge cannot be calculated due
to capacity issue."
NA Desktop

System should calculate and display the

correct shipping charge without error.
NA Desktop

System displays an error message:

"Shipping charge cannot be calculated due
to capacity issue." NA Desktop

System should prompt the seller to input

the vehicle number.
NA Desktop

System should prompt the seller to input

the driver’s name.
NA Desktop

System should prompt the seller to add the

Air Waybill (AWB) number.
NA Desktop
System should allow the seller to take a
printout of the invoice.
NA Desktop

Buyer should be notified of the order status

as "Out for Delivery" with shipping details,
including the AWB number.
NA Desktop

System should mark the order as

completed.
NA Desktop

System should prompts the seller to enter

the Proof of Delivery (POD) delivery code
provided by the buyer. NA Desktop

Buyer should be notified that the delivery

was successful, and the order status should
be updated to "Completed" in their order NA Desktop
details

System should displays an error message

indicating the POD is invalid and should
prompt for a correct entry. NA Desktop

System should display an error message

indicating that the POD must be provided
to complete the update. NA Desktop

System should detect the discrepancy and

triggers the RMA process.
NA Desktop

System should recalculate the shipping

charge based on the cart value, vehicle
type, and delivery pin code. NA Desktop

System does not trigger the RMA process,

and the order proceeds as normal.
NA Desktop
System triggers the RMA process for all
discrepancies and notifies both buyer and
seller accordingly. NA Desktop

The system automatically processes a

refund for the difference between the
charged amount and the correct shipping NA Desktop
charge and the buyer is notified of the
refund.
Buyer should be notified of the issue and
the steps being taken to resolve it.
NA Desktop

Seller should be notified of the shipping

charge discrepancy and the RMA process
initiated. NA Desktop

The system should send a final notification

to both the buyer and the seller, confirming
the resolution of the RMA.
NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

High

High

High

High

High

Medium

Medium
Medium

Medium

High

High

High

High

High

High

High
High

High

High

High

High

High

High

High

High
High

High

High

High

High

High

High

High

High
High

High

High

High

High

High

High

High

High

High
High

High

High

High

High
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_DM_001 Integration
Verify that the system
displays final order
amount and expected
MC-224
delivery date when
"Home Delivery" is
selected.

UT_DM_002 Integration
Verify that the system
prompts for a valid
MC-224
shipping address if
none is provided.

UT_DM_003 Integration

Verify the system

handles errors when
MC-224
calculating shipping
charges.

UT_DM_004 Integration
Verify that the
delivery mode
MC-224
remains selected after
editing the cart.

UT_DM_005 Integration
Verify that the system
updates the order
status to "Delivered"
MC-226
after successful
confirmation of
delivery.
UT_DM_006 Integration
Verify that the system
notifies the customer
to reschedule delivery
MC-226
if they are unavailable
at the time of
delivery.

UT_DM_007 Integration
Verify that the system
rejects an incorrect
MC-226 delivery confirmation
code and prevents
delivery completion.

UT_DM_008 Integration
Verify that the system
allows re-entry of the
correct confirmation
MC-226
code after a failed
attempt with the
wrong code.

UT_DM_009 Integration
Verify that the system
allows the customer
to select BOPIS when
MC-228
the delivery mode is
available for selected
items and location.

UT_DM_010 Integration
Verify that the system
disables the BOPIS
MC-228 option for multi-seller
orders and displays a
relevant message.

UT_DM_011 Integration
Verify that the system
displays an error
message when it
MC-228
encounters an issue
determining store
availability for BOPIS.

UT_DM_012 Integration
Verify that no shipping
charges are applied
MC-228 when BOPIS is
selected for eligible
items and location.
UT_DM_013 Integration Verify that the
customer can pick up
their BOPIS order in-
MC-229 store using a
confirmation code
within the pickup
timeline.
UT_DM_014 Integration
Verify that the system
cancels the order if
the customer does not
MC-229
pick up the order
within the pickup
timeline.

UT_DM_015 Integration
Verify that the system
applies a 5% penalty
if the customer
MC-229
requests order
cancellation after the
2-hour window.

UT_DM_016 Integration
Verify that the system
does not allow order
MC-229 cancellation within the
2-hour window
without penalty.

UT_DM_017 Integration
Verify that the
customer can
MC-230 successfully select
ROPIS and pay the 5%
advance.

UT_DM_018 Integration
Verify that the system
displays a message
MC-230 when there are
insufficient funds for
the 5% advance.

UT_DM_019 Integration
Verify that the system
handles payment
MC-230
gateway failure during
advance payment.

UT_DM_020 Integration
Verify that the system
cancels the ROPIS
MC-230 option if the store
does not offer ROPIS
for the selected items.
UT_DM_021 Integration
Verify that the
customer can
successfully pay the
MC-231
remaining balance
and pick up their
order.

UT_DM_022 Integration
Verify that the system
cancels the order and
forfeits the 5%
MC-231
advance if the
customer fails to pick
up within the timeline.

UT_DM_023 Integration
Verify that the system
handles customer
MC-231 cancellation requests
after the 2-hour
cancellation window.
 Total No. Of Test Cases : 23
High
Complexity Count :
5
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Add items to the cart.

2. Proceed to checkout.
3. Select "Home Delivery" as the delivery Customer has items in their cart.
mode.
4. Confirm the details.

1. Add items to the cart.

2. Proceed to checkout.
3. Select "Home Delivery" as the delivery Customer has not entered a valid
mode. shipping address.
4. Attempt to proceed without providing a
shipping address.
1. Add items to the cart.
2. Proceed to checkout.
3. Select "Home Delivery" as the delivery
Customer selects "Home Delivery" at
mode.
checkout.
4. Proceed to complete the order.
5. Simulate a system error calculating
shipping charges.
1. Add items to the cart.
2. Proceed to checkout.
3. Select "Home Delivery". Customer modifies the cart after
4. Go back to the cart to modify items. selecting delivery mode.
5. Return to checkout and verify the delivery
mode remains selected.

1. Ensure the seller has shipped the order.

2. The delivery reaches the customer’s
Seller has shipped the order.
address.
Customer is present at delivery
3. Customer provides the unique delivery
location.
confirmation code.
4. Confirm the code is accepted.
1. Ensure the seller has shipped the order.
2. The delivery person arrives at the Seller has shipped the order.
customer's address. Customer is unavailable at the
3. Customer is unavailable. delivery location.
4. Attempt to confirm the delivery.

1. Ensure the seller has shipped the order.

2. The delivery reaches the customer’s
address. Seller has shipped the order.
3. Customer provides an incorrect delivery Customer provides an incorrect code.
confirmation code.
4. Attempt to confirm the code.

1. Ensure the seller has shipped the order.

2. The delivery reaches the customer’s
address. Customer previously entered an
3. Customer first provides an incorrect code. incorrect code.
4. Customer re-enters the correct code.
5. Attempt to confirm the correct code.

1. Ensure the customer has items in the cart.

2. Proceed to checkout.
Items in the cart are eligible for
3. Select "Pay Online & Pick Up at Store" as
BOPIS.
the delivery mode.
4. Confirm pickup availability.

1. Ensure the customer has items from

multiple sellers in their cart.
Customer has items from multiple
2. Proceed to checkout.
sellers in the cart.
3. Attempt to select "Pay Online & Pick Up at
Store".

1. Ensure the customer has items in the cart.

2. Proceed to checkout. The system fails to determine store
3. Select "Pay Online & Pick Up at Store". availability for BOPIS.
4. The system encounters an error.

1. Ensure the customer has eligible items in

their cart. Customer has eligible items and
2. Proceed to checkout. selects BOPIS.
3. Select "Pay Online & Pick Up at Store".
1. Ensure the customer has received the
pickup confirmation code. Customer has received the
2. Visit the store within the pickup timeline. confirmation code and is within
3. Present the confirmation code. pickup timeline.
4. Store staff verifies the code.

1. Ensure the customer fails to visit the store

within the pickup timeline. Customer did not pick up within the
2. Attempt to pick up the order afterward. pickup timeline.
3. Check the order status in the system.

1. Ensure the customer wants to cancel the

order after the 2-hour window.
Customer requests order cancellation
2. Request cancellation.
after 2-hour window.
3. Check for penalty application and refund
process.

1. Ensure the customer has placed the order.

2. Request cancellation within the 2-hour Customer places order and requests
window. cancellation within 2-hour window.
3. Check for penalty.

1. Ensure the customer has items in their

cart.
2. Proceed to checkout.
Customer has sufficient funds and
3. Select "Reserve Online by Paying 5% in
selects ROPIS.
Advance & Pick Up at Store".
4. Confirm payment.
5. Check the expected pickup date.
1. Ensure the customer has items in their
cart.
2. Proceed to checkout.
Customer has insufficient funds.
3. Select ROPIS delivery mode.
4. Attempt to pay the 5% advance.
5. Check if funds are insufficient.
1. Ensure the customer selects ROPIS.
2. Attempt the 5% advance payment.
Payment gateway failure occurs
3. Simulate payment gateway failure.
during advance payment.
4. Check if the system handles failure
properly.

1. Ensure the customer adds non-ROPIS

eligible items to their cart.
Selected items are not eligible for
2. Proceed to checkout.
ROPIS.
3. Attempt to select ROPIS delivery mode.
4. Check if ROPIS is available for these items.
1. Ensure the customer has paid the 5%
advance.
2. Visit the store within the pickup timeline. Customer has already paid the 5%
3. Pay the remaining balance via cash or advance and selects ROPIS.
online.
4. Confirm order completion.

1. Ensure the customer has paid the 5%

advance.
2. Do not show up for pickup within the Customer fails to show up within the
specified timeline. pickup timeline.
3. Wait for the timeline to expire.
4. Check the order status.

1. Ensure the customer has paid the 5%

advance.
2. Wait until the 2-hour cancellation window Customer requests cancellation after
passes. the 2-hour window has passed.
3. Attempt to cancel the order.
4. Confirm the cancellation policy is applied.
 Medium Low
13 5

Test Device (for

Expected Results Test Data
mobile)

The system should display the final order

amount, including shipping charges, and
NA Desktop
show the expected delivery date based on
the location.

The system should prompt the customer to

enter or select a valid shipping address
NA Desktop
and prevent order completion until the
address is provided.

The system should display an error

message: "Unable to calculate shipping
NA Desktop
charges at this time. Please try again later
or contact support."

The system should retain "Home Delivery"

as the selected delivery mode even after NA Desktop
the cart is modified.

The system should confirm delivery,

update the order status to "Delivered," and
NA Desktop
send a notification confirming successful
delivery.
The system should fail the delivery attempt
and notify the customer to reschedule the NA Desktop
delivery.

The system should reject the incorrect

code and prevent delivery completion until NA Desktop
the correct code is provided.

The system should allow the customer to

re-enter the correct confirmation code,
NA Desktop
confirm the delivery, and update the order
status to "Delivered."

The system should confirm BOPIS

availability, display the expected pickup NA Desktop
date, and apply no shipping charges.

The system should disable the BOPIS

option and display the message "BOPIS is NA Desktop
not available for multi-seller orders."

The system should display an error

message, suggesting the customer try
NA Desktop
again later or choose a different delivery
mode.

The system should not apply shipping

charges when BOPIS is selected, and the
NA Desktop
total cost should reflect the absence of
shipping fees.
The store should provide the items, the
order status should be updated to
"Completed," and the customer should NA Desktop
receive a notification confirming order
completion.

The system may cancel the order, a 5%

penalty should be deducted, and the
NA Desktop
remaining amount should be refunded as
per policy.

The system should apply a 5% penalty and

NA Desktop
refund the remaining amount.

The system should not apply the 5%

penalty and allow cancellation as per policy NA Desktop
within the 2-hour window.

The system should confirm ROPIS

availability, calculate the 5% advance, and NA Desktop
display the expected pickup date.

The system should display an error

message stating, "Insufficient funds for
NA Desktop
advance payment," and prevent the
customer from proceeding.

The system should notify the customer of

the payment failure and prompt them to
NA Desktop
retry or choose a different payment
method.

The system should disable the ROPIS

option and notify the customer that "ROPIS NA Desktop
is not available for these items."
The system should allow the customer to
pay the remaining balance, provide the
NA Desktop
items, update the order status to
"Completed," and send a notification.

The system should forfeit the 5% advance,

cancel the order, and mark the status as
NA Desktop
"Cancelled" without issuing any further
refunds.

The system should forfeit the 5% advance

and cancel the order, notifying the
NA Desktop
customer that no additional refund will be
issued per policy.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

High

Low

Medium
Medium

High

Low

Medium

Medium

High

Low
Medium

High

Medium

Low

Medium

Medium

High

Low
Medium

Medium

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_MA_001 MC-60 Verify that all orders

are displayed in the
Unit "My Orders" section.

UT_MA_002 MC-60 Verify that order

details are displayed
Integration when a specific order
is clicked.

UT_MA_003 MC-60 Verify the message

displayed when no
Integration orders are placed.

UT_MA_004 MC-60 Verify the error

message displayed
Integration during a system issue.

UT_MA_005 MC-60 Verify automatic

logout upon session
Integration expiry.

UT_MA_006 MC-61 Verify that RFQ orders

are displayed in the
Integration "My Orders" section.
UT_MA_007 MC-61 Verify that RFQ order
details are displayed
when a specific RFQ
order is clicked.

Integration

UT_MA_008 MC-61 Verify the message

displayed when no
Integration RFQ orders are
placed.

UT_MA_009 MC-61 Verify the status of

RFQ orders that are
still under review.
Integration

UT_MA_010 MC-61 Verify the status

change for rejected
RFQ orders.
Integration

UT_MA_011 MC-61 Verify automatic

logout during RFQ
Integration order viewing due to
session expiry.

UT_MA_012 MC-62 Verify that orders can

be filtered by order
Integration status.

UT_MA_013 MC-62 Verify that orders can

be filtered by date
Integration range.

UT_MA_014 MC-62 Verify that specific

orders can be
Integration searched by ID or
keyword.

UT_MA_015 MC-62 Verify the message

displayed when no
Integration orders match the
search or filter.
UT_MA_016 MC-62 verify the error
message during a
Integration system error when
filtering or searching

UT_MA_017 MC-259 Verify that personal

information is
Integration displayed correctly.

UT_MA_018 MC-259 Verify that personal

details can be edited
and saved.
Integration

UT_MA_019 MC-259 Verify validation when

required fields are left
empty.
Integration

UT_MA_020 MC-259 Verify error handling

during a system
failure while saving.
Integration

UT_MA_021 MC-260 verify that saved

addresses are
Integration displayed correctly.

UT_MA_022 MC-260 Verify that an existing

address can be edited
Integration

UT_MA_023 MC-260 verify that the delete

option is disabled for
Integration addresses.

UT_MA_024 MC-260 Verify handling of

sync failures when
Integration updating an address.
UT_MA_025 MC-261 Verify that a user can
successfully add a
new address to their
Address Book.

Integration

UT_MA_026 MC-261 Verify system

behaviour when there
is a sync failure after
Integration adding an address.

UT_MA_027 MC-262 Verify that the user

can view a list of their
Unit past orders and RFQs.

UT_MA_028 MC-262
Verify that the user
can track an active
Integration
order's details.

UT_MA_029 MC-262 Verify that the user

can track an invalid
Integration
order's details.

UT_MA_030 MC-262 Verify system

behaviour when there
is an error fetching
Integration order details.

UT_MA_031 MC-263 Verify that the user

can view their
Integration submitted product
reviews.

UT_MA_032 MC-263 Verify that the user

can view their product
reviews immediately
Integration after submit
UT_MA_033 MC-263 Verify that the user
can view their product
reviews immediately
Integration after editing &
submitting it

UT_MA_034 MC-263 Verify if buyer can

delete their submitted
Integration review

UT_MA_035 MC-263 Verify that the user

can submit a review
for a seller after
Integration completing a
transaction.

UT_MA_036 MC-263 Verify system

behaviour when there
is an error saving
Integration review changes.

UT_MA_037 MC-264 Verify that an address

syncs successfully
between Marketplace
Integration and Utec platform.

UT_MA_038 MC-264 Verify that changes in

Utec platform are
Integration reflected in the
Marketplace.

UT_MA_039 MC-264 Verify system

behaviour when there
is a sync failure
Integration between Marketplace
and Utec.
 Total No. Of Test Cases : 39
High
Complexity Count :
6
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Log in as a buyer. Buyer has placed order

2. Navigate to "My Account".
3. Click on "My Orders".

1. . Log in as a buyer. Buyer is view order history

2. Navigate to "My Orders".
3. Click on a specific order from the order list.

1. Log in as a new buyer( first time user) Buyer is newly logged in

2. Navigate to "My Account".
3. Click on "My Orders".

1. Log in as a buyer. Buyer is logged in

2. Simulate a system error.
3. Navigate to "My Orders".

1. Log in as a buyer. buyer is logged in and viewing order

2. Navigate to "My Orders". history.
3. Wait for the session to expire.
4. Click on an order.

1. Log in as a buyer. Buyer has placed RFQ order

2. Navigate to "My Account".
3. Click on "My Orders".
4. Select "RFQ Orders".
1. Log in as a buyer. Buyer is logged in
2. Navigate to "My Orders".
3. Click on the RFQ orders tab.
4. Click on a specific RFQ order.

1. Log in as a buyer. buyer hasn’t placed any RFQ order

2. Navigate to "My Account".
3. Click on "RFQ Orders".

1. Log in as a buyer. buyer has placed an order

2. Navigate to "RFQ Orders".
3. Check the status of an RFQ order that is in
progress

1. Log in as a buyer. RFQ order of buyer is/was rejected

2. Navigate to "RFQ Orders".
3. Check the status of the rejected RFQ order.

1. Log in as a buyer.
2. Navigate to "RFQ Orders".
3. Wait for the session to expire.
4. Click on an RFQ order.

1. Log in as a buyer. Buyer has placed 3 or more orders

2. Navigate to "My Orders".
3. Select a status filter (e.g., Processing).

1. Log in as a buyer. Buyer has placed 3 or more orders

2. Navigate to "My Orders".
3. Select a date range filter.

1. Log in as a buyer. Buyer has placed 3 or more orders

2. Navigate to "My Orders".
3. Enter an order ID or keyword in the search
bar.

1. Log in as a buyer. Buyer has placed 3 or more orders

2. Navigate to "My Orders".
3. Apply a filter or search that returns no
results.
1. Log in as a buyer. Buyer has placed 3 or more orders
2. Simulate a system error.
3. Attempt to apply a filter or search.

1. Log in as a user. Buyer has logged in

2. Navigate to "My Profile".

1. Log in as a user. Buyer has logged in

2. Navigate to "My Profile".
3. Click "Edit".
4. Update a detail.
5. Save changes

1. Log in as a user. Buyer has logged in

2. Navigate to "My Profile".
3. Click "Edit".
4. Clear required fields.
5. Click on save.

1. Log in as a user. Buyer has logged in

2. Navigate to "My Profile".
3. Click "Edit".
4. Update details.
5. Simulate a system error on save

1. Log in as a user. Buyer has logged in

2. Navigate to "Address Book".

1. Log in as a user. Buyer has logged in

2. Navigate to "Address Book".
3. Click "Edit" next to a specific address.
4. Update details.

1. Log in as a user. Buyer has logged in

2. Navigate to "Address Book".
3. Attempt to delete an address.

1. Log in as a user. Buyer has logged in

2. Update an address.
3. Simulate a failure to sync with Utec.
1. Navigate to Address Book. Buyer has logged in
2. Click "Add New Address."
3. Fill in the address form:
- Name
- Street Address
- City
- State
- Zip Code
- Country
- Phone Number
4. Click "Submit."

1. Add a new address. Buyer has added a new address

2. Simulate a sync failure (e.g., disconnect
network).
3. Observe the system's response after
submission.

1. Navigate to My Orders. Buyer has placed RFQ order

2. Observe the displayed list of orders and
RFQs.

1. Navigate to My Orders.
2. Click the "Track" button next to the active
order. Buyer has an active order
3. Observe the tracking details.

1. Navigate to My Orders.
2. Click the "Track" button next to the
Buyer has not got active order
inactive order.

1. Attempt to refresh order details.

2. Simulate a system error (e.g., database
timeout).
Buyer has an active order

1. Navigate to My Product Reviews. buyer has submitted a review

2. Observe the displayed list of reviews. Admin should have approved the
review

1. Enter a review buyer is in pdp

2. refresh to PDP of the product
2. Observe if the submitted review is
displayed list of reviews.
1. edit a review buyer has submitted a review
2. refresh to PDP of the product
2. Observe if the edited review is displayed
list of reviews.

1. Navigate to My Product Reviews. buyer is in pdp

2. Observe the displayed list of reviews. should be able to view their
3. Click on delete icon submitted review

1. Navigate to the seller's profile. buyer has completed a transaction

2. Click "Leave Seller Review."
3. Rate the seller and provide feedback.
4. Click "Submit."

1. Attempt to save changes. Buyer is editing a review

2. Simulate a system error during save (e.g.,
network failure).

1. Save the address. User adds or updates an address in

2. Observe the Utec service platform for Marketplace.
updates.
3. Confirm receipt of address update
notification.

1. Update the address on Utec platform. User updates an address on the Utec
2. Observe the Marketplace for updates. platform.

1. Simulate a sync failure after User has added or updated an

adding/updating an address. address.
2. Observe the system's response.
 Medium Low
22 11

Test Device (for

Expected Results Test Data
mobile)

A list of all previous and current orders is

displayed chronologically by order date
with order ID, date, items, amount, and NA Desktop
status.
Complete details of the order are
displayed, including order ID, date, items,
quantity, price, shipping details, status, NA Desktop
and payment method.

A message indicating "No orders placed

yet" is displayed along with a link to start
shopping. NA Desktop

An error message stating "Unable to

retrieve your orders at this time. Please try
again later." is displayed. NA Desktop

The user is logged out and redirected to

the login page. After logging in, the user is
redirected back to the "My Orders" page. NA Desktop

A list of RFQ-based orders is displayed with

details such as RFQ ID, date of request,
items quoted, and current status.(e.g., NA Desktop
Quoted, Accepted, Rejected, In Progress).
buyer should see the complete details of
the RFQ order, including:
•RFQ ID
•Date of RFQ submission
•Items requested for a quote
•Quantity and custom specifications (if
any) NA Desktop
•Quoted price (if available)
•Status (Quoted, Accepted, Rejected)
•Seller information
•Delivery and payment terms

A message indicating "No RFQ orders

placed yet" is displayed along with a
suggestion to request a quote for custom NA Desktop
orders.

The status shows "In Progress" with a

message stating that the seller is reviewing
the RFQ and should be able to cancel or
modify my RFQ order while it is in progress NA Desktop
(if allowed by the system).

The status shows "Rejected" with a

message stating the reason for rejection (if
provided) and should have the option to
contact the seller or request a new quote. NA Desktop

The user is logged out and redirected to

the login page. After logging in, the user is
NA Desktop
redirected back to the "My Orders" page in
the RFQ section.

A list of orders matching the selected

status is displayed.
NA Desktop

A list of orders placed within the selected

timeframe is displayed.
NA Desktop

specific order(s) matching the search term

are displayed.
NA Desktop

A message indicating "No orders found for

the selected criteria" is displayed with an
option to clear the filter. NA Desktop
An error message stating "Unable to apply
filter/search. Please try again later." is
displayed. NA Desktop

All personal details like name, phone

number, and email are displayed correctly.
Cross verify with Backend NA Desktop

Updated information is saved and a

confirmation message is displayed.
Cross verify with Backend
NA Desktop

A validation error is displayed, preventing

the update.
Cross verify with Backend
NA Desktop

An error message is displayed asking the

user to try again.
Cross verify with Backend
NA Desktop

All saved addresses are displayed with

editable options.
NA Desktop

Updated address information is saved and

displayed in the address book.
NA Desktop

the delete option is disabled, and a

notification is shown that address removal
is not allowed. NA Desktop

An error message is displayed, and the

system should retry syncing the address.
NA Desktop
Address is added to the Address Book and
synced with the Utec marketplace

NA Desktop

Error message displayed indicating sync

failure. System retries sync automatically
until successful or user cancels.
NA Desktop

All past orders and RFQs displayed with

order numbers, status (e.g., pending,
dispatched), and an option to track each NA Desktop
order.

Real-time tracking details displayed,

including shipping status, estimated
NA Desktop
delivery, and any updates on the delivery
process.

track button should not be available for

NA Desktop
inactive or other orders

Error message displayed, prompting the

user to retry later.
NA Desktop

All submitted product reviews displayed,

with options to edit or delete each review.
NA Desktop

the user cannot view their product reviews

immediately after submitting it
NA Desktop
 the user cannot view their product reviews
immediately after submitting it

NA Desktop

buyer should be able to delete only their

submitted reviews
NA Desktop

Review should be saved successfully and

associated with the seller's profile.
NA Desktop

Error message displayed indicating failure

to save changes. User prompted to retry.
NA Desktop

Address should sync in real-time;

confirmation displayed that the address is
updated on both platforms.
NA Desktop

Marketplace should automatically reflect

changes made on Utec platform in real-
time. NA Desktop

User notified of sync issue; system should

automatically retry the sync process until
successful or user cancels the retry.
NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Low

Medium

High

Medium
Medium

Low

Medium

Medium

High

Medium

Medium

Medium

Low
Medium

Low

Medium

Medium

Medium

Low

Medium

Low

Medium
Medium

High

Low

Medium

Low

High

Low

Low
 Low

Medium

Medium

High

Medium

Medium

High
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

UT_SP_001 MC-148 Verify that a seller can

successfully add a
new product to the
catalogue.
Integration

UT_SP_002 MC-148 Verify that a seller can

successfully add a
new product to the
catalogue.
Integration

UT_SP_003 MC-148 Verify that a seller can

update existing
product details.

System

UT_SP_004 MC-148 Verify the system

enforces minimum
Integration and maximum price
validation.

UT_SP_005 MC-148 Verify the system

enforces maximum
price validation.
Integration
UT_SP_006 MC-149 Verify that a seller can
view all customer
System orders with relevant
details.

UT_SP_007 MC-149 Verify that a seller can

mark certain items as
shipped while leaving
others pending.
System

UT_SP_008 MC-149 Verify that the system

prevents a seller from
marking an order as
System shipped before
completing required
steps.

UT_SP_009 MC-149 Verify if buyer is

notified of partial
shipment

Integration

UT_SP_010 MC-149 Verify if seller can

mark order as shipped
without invoicing

System

UT_SP_011 MC-149 Verify Error Message

Displayed for Invalid
Shipment Action

Integration
UT_SP_012 MC-149 Verify complete
Invoicing and
Successfully Mark as
Shipped
System

UT_SP_013 MC-149 Verify if System Log of

Invalid Fulfilment
attempt

System

UT_SP_014 MC-150 Verify that a seller can

successfully configure
System shipping options.

UT_SP_015 MC-150 Verify that a seller can

view real-time
System inventory levels for
each product.

UT_SP_016 MC-150 Verify that a seller can

set alerts for low stock
System levels

UT_SP_017 MC-151 Verify that a seller can

upload a custom
banner and logo for
System their store.

UT_SP_018 MC-151 Verify that a seller can

modify the store
layout and see the
Integration changes immediately
after saving.
UT_SP_019 MC-152 Verify when seller
receives the RFQ from
buyer

Integration

UT_SP_020 MC-152 Verify the seller

providing Quote for
RFQ Request

Integration

UT_SP_021 MC-152 Verify if buyer get

notified of the quote
sent by seller

Integration

UT_SP_022 MC-153 Verify confirmation of

order before invoice
generation

System

UT_SP_023 MC-153 Verify invoice

generation once order
is confirmed

System
UT_SP_024 MC-153 Verify the invoice
details

Integration

UT_SP_025 MC-153 verify the scenario of

payment handling for
generated invoices

Integration

UT_SP_026 MC-153 Verify Order

Completion Before
Payment Collection
Integration

UT_SP_027 MC-153 Verify if seller can

mark Payment as
Received

Integration

UT_SP_028 MC-153 Verify Order

Completion Before
Payment Collection
Integration

UT_SP_029 MC-153 verify transaction

record in Payment
History

Integration
UT_SP_030 MC-154 Verify if seller can
access SKU
Management Page
Integration

UT_SP_031 MC-154 verify for seller.

Selected province and
map PIN Codes to SKU

Integration

UT_SP_032 MC-154 Verify SKU Availability

Based on Mapped PIN
Codes

Integration

UT_SP_033 MC-154 Verify Edit or Remove

Mapped PIN Codes for
a SKU

Integration

UT_SP_034 MC-161 Verify view order and

resolved pin code
tickets
Integration

UT_SP_035 MC-161 Verify view order and

resolved pin code
tickets
System
UT_SP_036 MC-161 Check Ticket Details
for Preorder/Post
order Complaints

Integration

UT_SP_037 MC-161 Verify filter Support

Tickets by Status

Integration

UT_SP_038 MC-161 Verify if seller is able

to access and view
the details of the
Unit routed complaint
ticket

UT_SP_039 MC-161 Verify if seller's

response is sent
successfully, and a
Integration confirmation message
is displayed.

UT_SP_040 MC-161 Verify if seller's

response is sent
successfully, and a
confirmation message
Integration is displayed.

UT_SP_041 MC-161 Verify if the issue

status is tracked
accurately, with all
changes recorded
Integration until the ticket is
marked as
"Resolved."
UT_SP_042 MC-161 Verify if RMA-related
complaint is
submitted
successfully, and a
Integration confirmation message
is displayed to the
buyer.

UT_SP_043 MC-161 Verify if RMA ticket

should appear in the
seller's ticket list,
marked appropriately,
Integration confirming direct
routing without Utec
admin intervention.

UT_SP_044 MC-161 Verify if seller

receives an
immediate notification
containing all relevant
Integration details about the RMA
request.

UT_SP_045 MC-161 Verify if system

indicates that the SLA
has been breached for
the specific ticket.
System

UT_SP_046 MC-161 Verify if the ticket is

automatically escalate
to the Utec admin,
and the ticket status
System reflects the change.
UT_SP_047 MC-161 Verify if the Utec
admin sees the
escalated ticket, and
a notification
Integration regarding the
escalation is logged in
the system.

UT_SP_048 MC-161 Verify if the ticket

status is changed to
"Resolved," and a
confirmation message
Integration is displayed.

UT_SP_049 MC-161 Verify if the buyer

receives a notification
confirming that the
issue has been
Integration resolved.

UT_SP_050 MC-161 Verify if the ticket is

marked as "Open"
again, and the seller
is notified of the ticket
reopening.
Integration
 Total No. Of Test Cases : 50
High
Complexity Count :
4
Test Cases Prepared By : Madhu Tulasydas
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Click "Add New Product." Seller is logged in and on the product

2. Fill in required fields: management page.
- Product Name: "New product"
- Description: "High-quality product."
- Price: "<<any amt>>"
- Variants: "Colour: Red, Size: Medium"
3. Click "Submit."

1. Click "Add New Product." Seller is logged in and on the product

2. Keep few in required fields empty: management page.
- Product Name: ""
- Description: "High-quality product."
- Price: ""
- Variants: "Colour: Red, Size: Medium"
3. Click "Submit."

1. Navigate to the product management seller has already listed a product

page.
2. Locate the product and click "Edit."
3. Update fields:
- Price: "24.99"
- Description: "Updated widget description."
4. Click "Save."

1. Navigate to the product management Seller is setting a price for the

page. product.
2. Click "Add New Product."
3. Enter a price below the minimum
4. Click "Submit."
1. Navigate to the product management Seller is setting a price for the
page. product.
2. Click "Add New Product."
3. Enter a price above the maximum (e.g.,
"$1000.00").
4. Click "Submit."
1. Click on "View Orders." Seller is logged in and on the order
2. Observe the order list displayed. management page.

1. Navigate to the order management page. A buyer has placed an order with
2. Select an order with multiple items. multiple items.
3. Choose items to ship and mark them as
"shipped."
4. Leave remaining items as "pending
shipment."
5. Click "Update Shipment."

1. Navigate to the order management page. The seller is processing an order.

2. Select an order that requires invoicing.
3. try to mark the order as "shipped."

1. Log in as the buyer. seller has completed marking items

2. Navigate to the notifications section. for partial shipment
3. Check for new notifications regarding the
order status.
4. Open the notification for the partial
shipment.
5. Verify that the notification includes details
about which items were shipped and which
are pending.

1. Log in as the seller. The seller is logged into the system

2. Navigate to the "Orders" section. and has an order ready for
3. Locate the specific order that needs processing.
processing.
4. Attempt to click the "Mark as Shipped"
button without completing the invoicing step.

1. Log in as the seller. The seller has attempted to mark an

2. Navigate to the "Orders" section. order as shipped without invoicing
3. Locate the specific order that needs
processing.
4. Attempt to click the "Mark as Shipped"
button without completing the invoicing step.
5. once the action is blocked, check for an
error message.
6. Verify that the error message clearly states
the requirement to complete invoicing before
shipping.
1. Log in as the seller. The seller has an order ready for
2. Navigate to the "Orders" section. processing and has completed the
3. Locate the specific order that needs invoicing.
processing.
4. Complete the invoicing for the order.
5. Attempt to click the "Mark as Shipped"
button.

1. Log in as the seller. The seller has attempted to mark an

2. Navigate to the "Orders" section. order as shipped without invoicing
3. Attempt to mark an order as shipped
without completing invoicing.
4. Check the system log or audit trail for
entries related to the failed attempt.
5. Verify that the log includes the timestamp,
seller ID, order ID, and reason for the failure.

1. Select available vehicles (e.g., Truck, Van). seller is logged in and on the shipping
2. Enter delivery pin codes (e.g., "560016, preferences page.
400012").
3. Click "Save Preferences."

1. Navigate to the inventory management Seller has multiple products listed.

section.
2. Observe the displayed list of products.
3. Check the inventory levels for each
product.
1. Select a product with low inventory. Seller is viewing inventory
2. Click "Set Alert" next to the product.
3. Enter alert threshold (e.g., 5 units).
4. Click "Save."

1. Click on "Upload Banner." Seller is logged in and on the store

2. Select an image file for the banner. customization page.
3. Click "Upload."
4. Click on "Upload Logo."
5. Select an image file for the logo.
6. Click "Upload."

1. Navigate to the store layout section. seller has customized their store
2. Change product arrangements (e.g., move layout previously
products around).
3. Add or modify promotional sections.
4. Click "Save Changes."
1. Log in as the seller. Seller is logged into the system and
2. Navigate to the RFQ requests section. has access to RFQ requests.
3. Check for new RFQ requests from buyers.
4. Select a new RFQ request.
5. Verify that the details of the RFQ request
are displayed (buyer details, requested
products/services, deadline).

1. From the RFQ request details, click on the The seller has received an RFQ
"Provide Quote" button. request
2. Enter pricing details, terms, and conditions
in the quote form.
3. Review the quote for accuracy.
4. Submit the quote.
5. Confirm submission and check for a
confirmation message.

1. Log in as the buyer. The seller has submitted a quote

2. Navigate to the notifications section.
3. Check for new notifications regarding RFQ
responses.
4. Open the notification for the provided
quote.
5. Verify that the quote details (pricing and
terms) are displayed correctly.

1. Log in as the seller. The seller is logged into the system

2. Navigate to the "Orders" section. and has an order that needs to be
3. Locate the specific order to be confirmed. confirmed.
4. Confirm the order status (e.g., change
from "Pending" to "Confirmed").
5. Verify that the order status updates
successfully.

1. In the order details view, click on the The seller has confirmed an order
"Generate Invoice" button.
2. Verify that a new invoice form opens with
order details pre-filled.
3. Check that all required fields (e.g., item
details, total amount, GST) are populated
correctly.
4. Click the "Submit" button to generate the
invoice.
1. Navigate to the "Invoices" section in the An invoice has been successfully
seller dashboard. generated for a confirmed order
2. Locate the newly generated invoice from
the list.
3. Open the invoice to view its details.
4. Verify that all information is accurate,
including itemized costs, total amount, GST,
and seller details.

1. Log in as the seller. An invoice has been generated .

2. Navigate to the "Invoices" section.
3. Locate the invoice that requires payment
collection.
4. Click on the "Collect Payment" button.
5. Enter payment details (amount, method,
etc.) and click "Submit."
6. Verify that the payment is recorded
successfully and the invoice status is updated
to "Paid."

1. Log in as the seller. seller is logged into the system and

2. Navigate to the "Orders" section. has a completed order.
3. Locate the specific completed order.
4. Verify that the order status is marked as
"Completed."

1. In the "Orders" section, locate the seller has a completed order

completed order.
2. Click on the "Mark Payment as Received"
button.
3. A confirmation dialog should appear.
4. Confirm the action to mark the payment as
received.

1. Navigate back to the "Orders" section. payment has been marked as

2. Locate the order for which payment was received
marked as received.
3. Check the order status.
4. Verify that the order status is now updated
to "Paid" or "Complete."

1. Log in as the seller. The payment has been marked as

2. Navigate to the "Payment History" section. received
3. Locate the transaction related to the order
for which payment was received.
4. Verify that the transaction details (order
ID, amount, date) are correctly recorded.
5. Check that the transaction status indicates
"Completed."
1. Log in as the seller. seller is logged into the system.
2. Navigate to the "SKU Management" section
from the dashboard.
3. Verify that the SKU management page
loads successfully.

1. Locate the SKU for which PIN codes need The seller is on the SKU management
to be mapped. page
2. Click on the SKU to open the mapping
options.
3. Select the appropriate province from the
dropdown menu.
4. Check the applicable PIN codes from the
provided list or input the relevant PIN codes
manually.
5. Click the "Save" button to confirm the
mapping.

1. Log out and then log in as a buyer. seller has mapped PIN codes to a SKU
2. Navigate to the product listing page.
3. Search for the SKU that has mapped PIN
codes.
4. Attempt to view the SKU details while
entering a PIN code that is both within and
outside the mapped regions.
5. Verify the availability message based on
the entered PIN code.

1. Navigate back to the SKU management seller has mapped PIN codes to a SKU
page (TC-001 has passed).
2. Locate the SKU with existing mapped PIN
codes.
3. Click on the SKU to view the mapping
details.
4. Edit the existing PIN codes or remove them
as needed.
5. Click the "Save" button to confirm
changes.

1. In the support section, locate the area The seller is logged into the CCP CRM
displaying tickets. system.
2. Review the list of support tickets (both
open and resolved).
3. Verify that all tickets routed by the Utec
admin are displayed correctly.

1. In the support section, locate the area seller is in the support section
displaying tickets.
2. Review the list of support tickets (both
open and resolved).
3. Verify that all tickets routed by the Utec
admin are displayed correctly.
1. Click on a specific ticket from the list. seller has accessed the support
2. Review the detailed information displayed section and can view tickets
for the selected ticket.
3. Verify that the ticket includes:
- Issue type (preorder/post order)
- Ticket status (open/resolved)
- Actions taken by the Utec admin before
routing to the seller.

1. In the support section, find the filtering The seller is viewing the list of
options for tickets. support ticket
2. Select filters for "Open" and "Resolved"
tickets.
3. Apply the filter and refresh the ticket list.
4. Verify that the displayed tickets match the
selected filter criteria.

1. Log in as the seller. seller is logged into the customer

2. Navigate to the "Support" or "Tickets" support system and has received a
section. routed complaint from the Utec
3. Locate the ticket that has been routed by admin.
the Utec admin.
4. Click on the ticket to view its details.

1. In the ticket details view, find the response seller has accessed the routed
section. complaint ticket
2. Type a response to the buyer’s query.
3. Click the "Send" or "Respond" button.
4. Verify that the system acknowledges the
response was sent.

1. . Log in as the buyer. seller has sent a response to the

2. Navigate to the chat or support section buyer’s query
where responses are received.
3. Check for new messages or notifications.
4. Open the relevant ticket or chat to view
the seller’s response.

1. In the ticketing system, locate the ticket seller has sent a response to the
after responding. buyer’s query
2. Monitor the ticket status field.
3. Change the status of the ticket as
necessary (e.g., "Pending," "Resolved").
4. Ensure the system logs all status changes
appropriately.
1. Log in as the buyer. The buyer is logged into the CCP CRM
2. Navigate to the "Support" or "RMA" section system.
of the CCP CRM system.
3. Fill out the RMA complaint form, providing
necessary details (e.g., order ID, reason for
return).
4. Submit the RMA request.

1. As a seller, log in to the CCP CRM system. RMA-related complaint has been
2. Navigate to the "Support" or "Tickets" submitted by the buyer
section.
3. Verify that the newly submitted RMA ticket
is visible in the seller's ticket list.
4. Check that the ticket is marked as an RMA-
related complaint and is not routed through
Utec admin.

1. Check the seller's notification section (e.g., An RMA-related complaint has been
email, system notifications) after the RMA submitted and routed to the seller
ticket has been routed.
2. Verify that the seller receives a notification
regarding the new RMA ticket.
3. Open the notification to review the details
about the RMA request (e.g., buyer
information, issue description).

1. Log in as the seller. A buyer has submitted a complaint,

2. Navigate to the "Support" or "Tickets" and the seller has not responded
section. within the SLA timeframe.
3. Locate the specific complaint ticket.
4. Check the timestamp of the complaint
submission and the SLA time frame.
5. Confirm that the time elapsed exceeds the
SLA limit without a response.

1. Ensure that the SLA breach condition is The seller has not responded to the
met (from TC-001). complaint within the SLA timeframe
2. Monitor the ticket system for automated
processes.
3. Verify that the system triggers an
escalation process after the SLA breach.
4. Check that the ticket is marked as
"Escalated" and routed to the Utec admin.
1. Log in as the Utec admin. An unresolved ticket has been
2. Navigate to the "Support" or "Escalated escalated to Utec admin
Tickets" section.
3. Verify that the escalated ticket is present
in the list.
4. Check the notification logs to confirm that
the admin received an alert about the
escalated ticket.

1. Log in as the seller. The seller has resolved the buyer's

2. Navigate to the "Support" or "Tickets" complaint and accessed the relevant
section. ticket.
3. Locate the ticket related to the buyer's
complaint.
4. Click on the ticket to view details.
5. Click the "Mark as Resolved" button.
6. Confirm the action when prompted.

1. Check the notification system (email, in- The seller has marked the ticket as
app notifications) as the buyer. resolved
2. Log in as the buyer.
3. Navigate to the "Notifications" or "Support"
section.
4. Verify that the buyer has received a
notification regarding the ticket resolution.

1. Log in as the buyer. The buyer has received a notification

2. Navigate to the "Support" or "Tickets" about the resolved ticket
section.
3. Locate the resolved ticket in the list.
4. Click on the ticket to view details.
5. Click the "Reopen Ticket" option if the
issue persists.
6. Confirm the reopening action when
prompted.
 Medium Low
34 12

Test Device (for

Expected Results Test Data
mobile)

Product is added to the catalogue and is

visible in the appropriate category.

NA Desktop

Product is should not added to the

catalogue and should not be visible in the
any category.

NA Desktop

Product listing reflects updated information

across the platform.

NA Desktop

System displays an error message

indicating the price needs to be within the
allowable range. NA Desktop

System displays an error message

indicating the price needs to be within the
allowable range.
NA Desktop
The system displays all orders, including
order details such as buyer information,
products ordered, payment status, and NA Desktop
shipping details.

The system allows the seller to mark

selected items as "shipped" and keeps the
remaining items as "pending shipment."

NA Desktop

The system prevents the action and

displays a message requiring the correct
steps to be followed before marking the
order as shipped. NA Desktop

The buyer should receive a notification

with accurate details of the shipped items
and those pending shipment.

NA Desktop

The system should prevent the action and

display a message indicating that invoicing
must be completed first.

NA Desktop

The error message should be clearly

displayed, outlining the requirement for
invoicing prior to marking the order as
shipped.

NA Desktop
The system should allow the seller to
successfully mark the order as shipped
without any errors.

NA Desktop

The system log should contain a record of

the invalid fulfilment attempt, detailing the
failure reason and relevant information.

NA Desktop

The system saves the seller’s shipping

preferences and applies them to all future
orders. NA Desktop

The system displays real-time inventory

levels for each product and allows the
seller to set alerts for low stock. NA Desktop

The system sets the low stock alert and

notifies the seller when inventory levels fall NA Desktop
below the specified threshold.

The system displays the uploaded banner

and logo on the seller’s store page for
buyers to see.
NA Desktop

The store reflects the changes immediately

after saving, displaying the new product
arrangements and promotional sections
correctly. NA Desktop
The seller should see the RFQ request
details accurately displayed.

NA Desktop

The quote should be submitted

successfully, and a confirmation message
should be displayed. The quote should be
saved in the system.
NA Desktop

The buyer should receive a notification

with the correct quote details, enabling
them to review and negotiate.

NA Desktop

The order should be confirmed, and the

status should be updated in the system.

NA Desktop

The system should generate the invoice

with all required details, including GST, and
display a confirmation message.

NA Desktop
The invoice details should match the
confirmed order, including correct GST
calculations.

NA Desktop

The payment should be recorded, and the

invoice status should update to "Paid" in
the system.

NA Desktop

The order should be marked as

"Completed," indicating it is ready for
payment collection.
NA Desktop

The payment should be marked as

"Received," and a confirmation message
should be displayed.

NA Desktop

The order status should be updated to

reflect that payment has been received
and the transaction is complete.
NA Desktop

The transaction record should accurately

reflect the payment details, and the status
should indicate that the transaction is
complete.

NA Desktop
The SKU management page should be
displayed with options to manage SKUs.
NA Desktop

The selected PIN codes should be

successfully mapped to the SKU, and a
confirmation message should be displayed

NA Desktop

he SKU should only be available for

purchase if the buyer's PIN code matches
the mapped regions. An appropriate
message should be displayed for non-
matching PIN codes.
NA Desktop

The updated mapping of PIN codes should

be saved successfully, and a confirmation
message should be displayed. The changes
should reflect in the SKU availability.

NA Desktop

The support section should be displayed,

providing access to support tickets.

NA Desktop

The system should show a comprehensive

list of support tickets, including both open
and resolved statuses.
NA Desktop
The detailed view of the ticket should
include all specified information accurately.

NA Desktop

The ticket list should update to show only

the tickets that correspond to the selected
status filters (open or resolved).

NA Desktop

Seller should be able to access and view

the details of the routed complaint ticket.

NA Desktop

seller's response should be sent

successfully, and a confirmation message
should be displayed.
NA Desktop

buyer should see the seller's response

promptly in the ticket or chat section.

NA Desktop

The issue status should be tracked

accurately, with all changes recorded until
the ticket is marked as "Resolved."

NA Desktop
The RMA-related complaint should be
submitted successfully, and a confirmation
message should be displayed to the buyer.

NA Desktop

RMA ticket should appear in the seller's

ticket list, marked appropriately,
confirming direct routing without Utec
admin intervention.
NA Desktop

The seller should receive an immediate

notification containing all relevant details
about the RMA request.

NA Desktop

The system should indicate that the SLA

has been breached for the specific ticket.

NA Desktop

The ticket should automatically escalate to

the Utec admin, and the ticket status
should reflect this change.

NA Desktop
The Utec admin should see the escalated
ticket, and a notification regarding the
escalation should be logged in the system.

NA Desktop

The ticket status should change to

"Resolved," and a confirmation message
should be displayed.

NA Desktop

The buyer should receive a notification

confirming that the issue has been
resolved.

NA Desktop

The ticket should be marked as "Open"

again, and the seller should be notified of
the ticket reopening.

NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Medium

High

High
Medium

Medium

High

Medium

Low

Low
Medium

Medium

Medium

Medium

Medium

Medium

Medium
Medium

High

Low

Low

Medium
Medium

Medium

Low

Medium

Medium

Medium
 Low

Medium

Medium

Medium

Low

Medium
Medium

Medium

Low

Medium

Medium

Medium
 Low

Medium

Low

Medium

Medium
 Low

Medium

Low

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

Verify if the user can

create a new product
category

UT_AP_001 Integration MC-63

Verify if the user can

edit an existing
product category
UT_AP_002 Integration MC-63

Verify if an error is
displayed when the
user miss entering
UT_AP_002 Integration MC-63 mandatory fields (e.g.,
category name),

Verify if a category
can be deleted
without affecting
UT_AP_003 Integration MC-63 unrelated categories.

Verify if user can add

a new SKU to a
UT_AP_004 Integration MC-63 product
 Verify if user can edit
a SKU to a product
UT_AP_005 Integration MC-63

Verify if user can

delete a SKU to a
UT_AP_006 Integration MC-63 product

Verify when user tries

to add a SKU that
already exists in the
UT_AP_007 Integration MC-63 system, error has to
be prompted

Verify if the user is

able to search for a
UT_AP_008 Integration MC-63 product by SKU

Verify if user sets a

product's price above
the defined threshold
UT_AP_009 Integration MC-63 an error is triggered

Verify if user sets a

product's price below
the defined threshold
UT_AP_010 Integration MC-63 an error is triggered

Verify if user can

create a new admin
role with specific
permissions
UT_AP_011 Unit MC-64

Verify if user can

assign an existing role
to a user
UT_AP_012 Unit MC-64
 Verify when the admin
tries to delete a role
that is currently
UT_AP_013 Integration MC-64 assigned to users, a
warning message is
received

Verify when the user

tries to access a
restricted section

UT_AP_014 Integration MC-64

Verify if the admin

users can reset their
passwords based on
UT_AP_015 Integration MC-64 role permissions

Verify if user can

generate a sales
report for a specific
UT_AP_016 Integration MC-65 date range.

Verify if user can

generate a sales
UT_AP_017 Integration MC-65 report for No specific
date range.

Verify if the sales can

be reported based on
UT_AP_018 Integration MC-65 different Sales
parameters

Verify the accuracy of

customer behaviour
via reports like
UT_AP_019 Integration MC-65 abandoned carts etc.
 Verify if the admin
can export the large
set of reports
UT_AP_020 Integration MC-65

Verify if approvers
receive notifications
when actions require
UT_AP_021 Integration MC-65 their approval.

Verify if the newly

created products
require approval
UT_AP_022 Integration MC-65 before being
displayed in the front
end

Verify if the editing of

existing products go
through an approval
UT_AP_023 Integration MC-65 process.

Verify if the newly

created CMS pages
require approval
UT_AP_024 Integration MC-65 before being
published

Verify if the editing of

existing CMS pages go
through an approval
process
UT_AP_025 Integration MC-65

Verify if the order

modifications require
approval

UT_AP_026 Integration MC-65

 Verify if a product,
CMS page, or order
can be rejected in the
approval workflow
UT_AP_027 Integration MC-65

Verify if a rejected
product, CMS page, or
order can be
resubmitted after
UT_AP_028 Integration MC-65 changes

Verify if the approval

history of each action
is logged and
UT_AP_029 Integration MC-65 recorded

Verify if user can

configure GST rates
for different products
UT_AP_030 System MC-65

Verify if the correct

GST rate is applied
during checkout
UT_AP_031 Integration MC-65

Verify if invoices
include accurate GST
details.
UT_AP_032 Integration MC-65

Verify if financial
reports include GST
breakdowns

UT_AP_033 Integration MC-65

 Verify if the admin
can configure system
alerts

UT_AP_034 Integration MC-68

Verify if the admin

can customize the
email template for
new orders

UT_AP_035 Integration MC-68

Verify if the customer

receives the order
confirmation email
after placing an order
UT_AP_036 Integration MC-68

Verify if the customer

receives the shipping
confirmation email
after order is shipped
UT_AP_037 Integration MC-68

Verify if the customer

receives the shipping
confirmation email
after order is
UT_AP_038 Integration MC-68 Cancelled
 Verify if the admin
can configure push
notifications for
customer events
UT_AP_039 Integration MC-68

Verify if customers
receive a push
notification when a
UT_AP_040 Integration MC-68 new order is placed

Verify if customers
receive a push
notification when they
abandon their cart
UT_AP_041 Integration MC-68

Verify if customers
receive a push
notification when their
UT_AP_042 Integration MC-68 order is shipped

Verify if a customer
can submit an RFQ for
a single seller's
product
UT_AP_043 Integration MC-66

Verify if a seller can

view a list of RFQs
submitted by
UT_AP_044 Integration MC-66 customers

verify if a seller can

respond to an RFQ
with pricing and
comments
UT_AP_045 Integration MC-66
 Verify if a seller can
approve or reject a
customer's RFQ.
UT_AP_046 Integration MC-66

Verify if a customer
can submit an RFQ for
a product available
UT_AP_047 Integration MC-66 from multiple sellers

Verify if sellers can

view their RFQs for a
multi-seller product
UT_AP_048 Integration MC-66

Verify if sellers can

view a list of RFQs
submitted by
UT_AP_049 Integration MC-66 customers

verify if sellers can

respond to an RFQ
with pricing and
comments
UT_AP_050 Integration MC-66

verify if customer can

view responses from
multiple sellers.

UT_AP_051 Integration MC-66

Verify if each seller

can approve or reject
a customer's RFQ
UT_AP_052 Integration MC-66 independently
 Verify if both sellers
and customers can
view RFQ history.

UT_AP_053 Integration MC-66

Verify if the user can

view a list of all RMC
UT_AP_054 Unit MC-66 orders

Verify if the order can

be filtered by status
UT_AP_055 Integration MC-66

Verify if the user can

view details of a
UT_AP_056 Integration MC-66 specific order.

Verify if the Admin/

Seller can search for a
specific order using
UT_AP_057 Integration MC-66 the order ID or
customer name.

Verify if the user can

edit an order
UT_AP_058 Integration MC-66

Verify if the user can

delete an order
UT_AP_059 Integration MC-66

Verify if users with

different roles can
only access
UT_AP_060 Unit MC-66 functionalities
appropriate to their
permissions.

Verify if the user can

filter orders based on
UT_AP_061 Integration MC-66 a specific date range.
 Verify if the user can
export order data to a
UT_AP_062 Integration MC-66 CSV or Excel file.

Verify that the user

can view a list of all
UT_AP_064 Unit MC-67 customer accounts.

Verify that the user

can view detailed
UT_AP_065 Unit MC-67 information for a
specific customer.

Verify that the user

can edit the details of
a customer account.
UT_AP_066 Unit MC-67

verify that the user

can view the order
UT_AP_067 Integration MC-67 history for a specific
customer.

Verify that the user

can add a new
address for a specific
UT_AP_068 Integration MC-67 customer.

Verify if that the user

can delete a customer
UT_AP_069 Integration MC-67 account if permitted.
 Total No. Of Test Cases : 69
High
Complexity Count :
42
Test Cases Prepared By : <tester>
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Navigate to Catalogue > Categories. Admin user logged in, at least one
2. Click on Add Root Category or Add product exists in the catalogue
Subcategory.
3. Enter category details such as name, URL
key, and description.
4. Assign products to this newly created
category.
5. Save the category.

1. Navigate to Catalogue > Categories. Admin user logged in, at least one
2. Select an existing category. category exists
3. Change the category name, URL key, and
other settings.
4. Save the changes.

1. Navigate to Catalogue > Categories. Admin user logged in, at least one
2. Select an existing category. category exists
3. remove the category name or any other
required field
4. Save the changes.

1. Navigate to Catalogue > Categories. Admin user logged in, at least two
2. Select a category and click Delete. categories exist
3. Confirm the deletion.

1. Navigate to Catalogue > Products. Admin user logged in, No Products

2. Open a product for editing. exits
3. Add the SKU field.
4. Save the product.
1. Navigate to Catalogue > Products. Admin user logged in, at least one
2. Open a product for editing. product exists
3. Update the SKU field.
4. Save the product.

1. Navigate to Catalogue > Products. Admin user logged in, at least one
2. Open a product for editing. product exists
3. delete the SKU field.
4. Save the product.

1. Navigate to Catalogue > Products. Admin user logged in, at least one
2. Open a product for editing. product exists
3. Update the SKU field to the same name as
the SKU
4. Save the product.

1. Navigate to Catalogue > Products. Admin user logged in, products with
2. Use the SKU search filter to search for a unique SKUs exist
specific SKU.

1. Navigate to Catalogue > Products. Admin user logged in, pricing

2. Open a product for editing. threshold is set
3. Set the product price above the allowed
range
4. Save the product

1. Navigate to Catalogue > Products. Admin user logged in, pricing

2. Open a product for editing. threshold is set
3. Set the product price below the allowed
range
4. Save the product

1. Navigate to System > Permissions > User User is logged in as Admin

Roles.
2. Click on Add New Role.
3. Enter the Role Name and Role Information.
4. Set the Role Permissions by selecting
specific system resources
5. Save the new role

1. Navigate to System > Permissions > All User is logged in as Admin. At least
Users. one role should exist
2. Select a user to edit or click Add New User.
3. In the User Role section, assign the user to
a specific role
4. Save the user
1. Navigate to System > Permissions > All User is logged in as Admin.
Users.
2. Select a user to delete a User.
3. Save the user

1 Navigate to System > Permissions > User User is not an Admin user
Roles.
2 Click on Add New Role.
3 Define a custom role that has access to
view products but not edit.
4 Assign the role to a user.
5 Log in as the user and try to view and edit
products.

1. Log in as an admin user with password Admin user logged in, user role with
reset permissions. password reset permissions assigned.
2. Navigate to Account Settings.
3. Change the password.
4. Log out and log in with the new password.

1. Navigate to Reports > Sales > Orders. Admin user logged in, at least one
2. Select a specific date range completed order should be there in
3. Click Refresh to generate the report. the system.

1. Navigate to Reports > Sales > Orders. Admin user logged in, at least one
2. Do not select any specific date range completed order should be there in
3. Click Refresh to generate the report. the system.

1. Navigate to Reports > Sales Report Admin user logged in, orders
2. Generate the report. completed should exist in the system
3. Analyse the detailed report for data
grouped by Sales methods.

1. Navigate to Reports > Marketing > Admin user logged in, at least one
Abandoned Carts. abandoned cart should be in the
2. Generate the report for the last 30 days. system.
3. Review the number of abandoned carts,
products in carts, and cart totals.
1. Navigate to Reports > Marketing > Admin user logged in
Abandoned Carts.
2. Generate the report for the last 30 days.
3.Select Export to option as CSV or PDF and
4. click on Export

Log in as the approver and check the Admin user logged in, approval
notifications via email or system notifications. workflow is enabled

1. Log in as a catalogue manager. Admin user logged in, approval

2. Navigate to Catalogue > Products and click workflow for product creation is
Add New Product. enabled
3. Fill in product details
4. Save the product as a draft or submit it for
approval.

1. Log in as a catalogue manager. Admin user logged in, approval

2. Navigate to Catalogue > Products and workflow for product edit is enabled
select an existing product.
3. Make changes to the product details (e.g.,
price, description).
4. Submit the changes for approval.

1. Log in as a manager. Admin user logged in, approval

2. Navigate to Content > Pages and click Add workflow for CMS page creation is
New Page. enabled
3. Fill in the details for the new CMS page
(e.g., title, content).
4. Submit the CMS page for approval.

1. Log in as a manager. Admin user logged in, approval

2. Navigate to Content > Pages and select an workflow for CMS page edit is enabled
existing page.
3. Fill in the details for the new CMS page
4. Submit the CMS page for approval.

1. Log in as a customer service Admin user logged in, approval

representative. workflow for order modifications is
2. Navigate to Sales > Orders and select an enabled
existing order.
3. Make modifications to the order
4. Submit the changes for approval.
1. Log in as a catalogue manager and submit Admin user logged in, approval
a new product for approval. workflow is enabled
2. Log in as the approver and reject the
product submission.
3. Provide a reason for rejection and submit
the decision.

1. Log in as the catalogue manager. Admin user logged in, a previously

2. Edit the rejected product or page to rejected product or page exists
address the rejection reasons.
3. Resubmit the product or page for approval

1. Log in as a catalogue manager and submit Admin user logged in, approval
a product for approval. workflow is enabled.
2. Log in as the approver and approve or
reject the product.
3. Review the approval history

1. Log in as an admin and navigate to Stores Admin user logged in

> Taxes > Tax Zones and Rates.
2. Click Add New Tax Rate and configure GST
rates based on the product type or region
3. Save the tax rate and assign it to a Tax
Rule

1. Log in as a customer and add a GST- GST is configured for the products, a
applicable product to the cart. customer is purchasing from a GST-
2. Proceed to checkout and enter a billing applicable region
address in a region where GST applies.
3. Review the Order Summary.

1. Log in as an admin and navigate to Sales > Customer has placed an order with
Orders. GST applied, admin has access to
2. Select a completed order and click Invoice. invoice generation
3. Review the generated invoice details.

1. Log in as an admin and navigate to Admin has access to financial reports,

Reports > Sales > Orders. orders with GST applied
2. Generate a financial report for a specific
date range where GST orders were placed.
3. Review the financial report for GST details.
1. Log in as an admin and navigate to Stores Admin user is logged in.
> Configuration > Advanced > Admin.
2. Scroll to the Admin Notifications section
and configure the types of alerts to be
displayed
3. Save the configuration

1. Log in as an admin and navigate to Admin user is logged in.

Marketing > Communications > Email
Templates.
2. Click Add New Template and select New
Order Confirmation from the Load default
template dropdown.
3. Customize the email content, including
branding, layout, and dynamic order details.
4. Save the template.

1. Log in as a customer and place an order. Customer has placed an order

2. Complete the checkout process.
3. Check the customer’s email inbox for the
order confirmation email.

1. Log in as an admin and mark an order as Order has been shipped

Shipped in the Orders section.
2. Check the customer’s email inbox for the
shipping confirmation email.

1. Log in as an admin and mark an order as Order has been Cancelled

Cancelled in the Orders section.
2. Check the customer’s email inbox for the
Cancelled email.
1. Log in as an admin and navigate to Stores Admin user is logged in, push
> Configuration > Push Notifications. notifications are enabled in the
2. Configure push notifications for specific system.
customer events
3. Save the configuration

1. Log in as a customer and place an order. New order notification should be

2. Complete the checkout process. configured
3. Check the device/browser for the new
order push notification.

1. Log in as a customer and add items to the All notification should be configured
cart.
2. Leave the website without completing the
purchase.
3. Wait for the configured delay for
abandoned cart notifications.
4. Check the device/browser for the
abandoned cart push notification.

1. Log in as an admin and mark an order as order shipment notification is

Shipped in the Orders section. configured
2. Check the customer’s device/browser for
the order shipment push notification.

1. Log in as a customer and navigate to a A product is available from a single

product from a single seller. seller for RFQ
2. Click on the Request for Quotation (RFQ)
button.
3. Fill in the RFQ form with required details
4. Submit the RFQ.

1. Log in as a single seller and navigate to seller has received RFQs from
the Seller Dashboard. customers
2. Go to the RFQ Management section.
3. View the list of submitted RFQs, including
details such as product, customer name, and
status.

1. Log in as a single seller and navigate to seller has received RFQs from
the RFQ Management section. customers
2. Select an RFQ from the list.
3. Enter the pricing, comments, and any
additional terms for the requested product.
4. Submit the response.
1. Log in as a single seller and navigate to seller has received RFQs from
the RFQ Management section. customers
2 Select a pending RFQ.
3. Approve or reject the RFQ based on the
terms.
4. Submit the decision.

1. Log in as a customer and navigate to a The product is available from multiple

product listed by multiple sellers. sellers for RFQ
2. Click on the Request for Quotation (RFQ)
button.
3. Fill in the RFQ form with required details 4.
Submit the RFQ.

1. Log in as a seller and navigate to the Seller Multiple sellers have received RFQs
Dashboard. from customers for the same product
2. Go to the RFQ Management section.
3. View the list of RFQs specific to their
listings, including details such as product,
customer name, and status.

1. Log in as a seller and navigate to the Seller multiple sellers has received RFQs
Dashboard. from customers
2. Go to the RFQ Management section.
3. View the list of submitted RFQs, including
details such as product, customer name, and
status.

1. Log in as seller and navigate to the RFQ multiple sellers has received RFQs
Management section. from customers
2. Select an RFQ from the list.
3. Enter the pricing, comments, and any
additional terms for the requested product.
4. Submit the response.

1. Log in as a customer and navigate to the multiple sellers has responded to

RFQ Management section in the account RFQs from customers
dashboard.
2. View the responses from different sellers.
3. Compare the pricing, comments, and
terms provided by each seller.

1. Log in as a single seller and navigate to multiple sellers has responded to

the RFQ Management section. RFQs from customers
2 Select a pending RFQ.
3. Approve or reject the RFQ based on the
terms.
4. Submit the decision.
1. Log in as a seller and navigate to the RFQ RFQs have been submitted,
Management section. responded to, and completed.
2. View the history of RFQs, including
submission dates, responses, and statuses.
3. Log in as a customer and navigate to the
RFQ Management section in the account
dashboard.
4. View the history of submitted RFQs and
seller responses.

Navigate to the "Orders" section User is logged in as Admin

1. Navigate to the "Orders" section. User is logged in as Admin

2. Select a status filter (e.g., "Pending").
3. Click "Apply Filter."

1. Navigate to the "Orders" section. User is logged in as Admin

2. Click on a specific order from the list.

1. Navigate to the "Orders" section. User is logged in as Admin

2. Enter a valid order ID or customer name in
the search bar.
3. Click "Search."

1. Navigate to the "Orders" section. User is logged in as Admin

2. Select an order to edit.
3. Modify the required fields (e.g., quantity,
delivery date).
4. Save the changes.

1. Navigate to the "Orders" section. User is logged in as Admin or should

2. Select an order to delete. have right permissions
3. Click on "Delete" and confirm the action.

Navigate to the "Orders" section. User is logged in with a specific role

(e.g., Admin, User).

1. Navigate to the "Orders" section. User is logged in

2. Select a start and end date in the date
filter.
3. Click "Apply Filter."
1. Navigate to the "Orders" section. User is logged in as Admin or should
2. Click on "Export Orders." have right permissions

Navigate to Customers > All Customers in the User is logged in as an admin or has
Magento admin panel appropriate permissions.

1. Navigate to Customers > All Customers. User is logged in.

2. Click on a specific customer from the list.

1. Navigate to Customers > All Customers. User is logged in and has permission
2. Select a customer and click on "Edit." to edit customer details.
3. Modify customer information (e.g., name,
email, address).
4. Click "Save."

1. Navigate to Customers > All Customers. User is logged in.

2. Select a customer and click on "Order
History."

1. Navigate to Customers > All Customers. User is logged in and has permission
2. Select a customer and click on to edit customer addresses.
"Addresses."
3. Click on "Add New Address."
4. Fill in the address details and click "Save."

1. Navigate to Customers > All Customers. User is logged in and has permission
2. Select a customer to delete. to delete customers.
3. Click on "Delete" and confirm the action.
 Medium Low
26 1

Test Device (for

Expected Results Test Data
mobile)

User should be able to create a new

category successfully. The category should
appear in the catalogue tree. The products
should appear under this newly created
category in the frontend. NA Desktop

The category should be updated

successfully. All the changes should reflect
on the frontend. Products should remain
properly assigned to this category. NA Desktop

The user should receive an error message

indicating the required fields need to be
filled.
NA Desktop

The category should be removed from the

catalogue tree.
The products under the deleted category
should either be reassigned or remain NA Desktop
uncategorized. Other categories should
remain unaffected

The product should be added successfully.

The SKU should appear in the product list
and should be reflected in the marketplace NA Desktop
inventory.
The product should be updated
successfully. The SKU should appear in the
product list and should be reflected in the NA Desktop
marketplace inventory.

The product should be deleted

successfully. The SKU should appear in the
product list and should be reflected in the NA Desktop
marketplace inventory.

The product should not be updated. User

should receive an error message indicating
that the SKU is already in use, be prompted
to enter a unique SKU. NA Desktop

The search results should only display the

product that matches the SKU.
NA Desktop

An error message should be displayed,

indicating that the price exceeds the
threshold. The product should not be saved
with the invalid price. NA Desktop

An error message should be displayed,

indicating that the price less than the
threshold. The product should not be saved
with the invalid price. NA Desktop

The new role should be created

successfully. The role should appear in the
User Roles list with the specified
permissions.
NA Desktop

The user should be assigned to the

specified role. The role should define the
user’s access control in the admin panel.
NA Desktop
A warning message should be displayed to
the user.

NA Desktop

The user should be able to view products

but not edit them. An "Access Denied"
message should appear if the user tries to
edit a product.
NA Desktop

The admin user should be able to reset

their password. The new password should
work on the next login.
NA Desktop

A sales report should be able to generate

and view detailed reports on sales,
including revenue, best-selling products,
and sales trends. NA Desktop
The data should match the actual sales
orders for that period.

A sales report should NOT be generated

and the system should display a message
indicating that no data is available for the NA Desktop
chosen range.

The report should display a breakdown of

sales based on the including revenue, best-
selling products, and sales trends. NA Desktop

The report should be able to view insights

such as most frequently viewed products,
customer purchase patterns, and
engagement metrics. NA Desktop
The report should be exported efficiently
and notify the admin once the export is
complete
NA Desktop

The approver should receive a notification,

notifying them of the pending approval
request.
The notification should contain details NA Desktop
about the request and a link to the pending
action.
The product should be saved & in a
pending state, awaiting approval.
A notification should be sent to the
designated approver for review. NA Desktop
The product should not appear on the
front-end store until it is approved.

The product changes should be saved & in

a pending state, awaiting approval.
The existing product data should remain
live on the store until the changes are NA Desktop
approved.
A notification should be sent to the
designated approver for review.
The CMS page should be saved in a
pending state, awaiting approval.
A notification should be sent to the
designated approver for review. NA Desktop
The page should not appear on the front
end until it is approved.

The changes should be saved in a pending

state, awaiting approval.
The existing page content should remain
live until the changes are approved.
A notification should be sent to the NA Desktop
designated approver for review.

The order modifications should be saved in

a pending state, awaiting approval.
The existing order data should remain
unchanged until the modifications are
approved. NA Desktop
A notification should be sent to the
designated approver for review.
The product should be moved to a rejected
state along with the reason specified.
The submitter should receive a notification
about the rejection.
The product should not appear on the front NA Desktop
end.

The product or page should move back into

the pending state after resubmission.
The changes should be sent for approval,
and notifications should be triggered
accordingly NA Desktop
The product or page should not appear on
the front end until it is approved.

The system should log all approval actions

(submission, approvals, rejections) with
timestamps.
The history should be accessible from the NA Desktop
product or CMS page’s approval section.

The GST rate should be saved successfully.

The rate should be applied to relevant
products during checkout.
NA Desktop

The correct GST rate should be applied to

the product's price. The total amount
should include the product price plus the
GST amount. NA Desktop

The invoice should display the product

prices, GST breakdown, total GST amount,
and any other relevant tax details.
NA Desktop

The report should display accurate

financial data, including total sales, GST
collected, and any GST refunds.

NA Desktop
The system alerts configuration should be
saved successfully.
The specified system alerts should appear
on the Admin Dashboard or as popup
notifications when triggered. NA Desktop

The customized email template should be

saved successfully.
The new email template should be used for
future order confirmation emails.

NA Desktop

The order confirmation email should be

delivered to the customer’s email address.
The email should contain the correct order
details and use the customized template.
NA Desktop

The customer should receive the shipping

confirmation email with the correct order
and tracking details.
The email should use the customized
template, including the Cancelled NA Desktop
information and amount to be refunded

The customer should receive the Cancelled

confirmation email with the correct order
details.
The email should use the customized
template, including the shipping NA Desktop
information and branding
Push notification settings should be saved
successfully.
Notifications should be triggered based on
the configured events
NA Desktop

The customer should receive a push

notification confirming the new order
placement.
The notification should contain relevant NA Desktop
order details

The customer should receive a push

notification reminding them about their
abandoned cart.
The notification should contain details of
the items left in the cart and a link to NA Desktop
return to the website

The customer should receive a push

notification indicating that their order has
been shipped.
The notification should include shipment NA Desktop
tracking details.

The RFQ should be submitted successfully,

and a confirmation message should
appear.
The seller should receive a notification
about the new RFQ. NA Desktop

The seller should see a complete list of

RFQs with relevant details. The status of
each RFQ should be correctly displayed
NA Desktop

The seller should be able to submit a

response with pricing and comments.
The customer should receive a notification
of the seller's response.
NA Desktop
The seller should be able to approve or
reject the RFQ.
The customer should receive a notification
about the approval or rejection. NA Desktop

The RFQ should be submitted successfully,

and a confirmation message should
appear.
All relevant sellers should receive a NA Desktop
notification about the new RFQ.

Each seller should see only the RFQs

relevant to their product listing.
The status of each RFQ should be correctly
displayed. NA Desktop

Each seller should see a complete list of

RFQs with relevant details. The status of
each RFQ should be correctly displayed
NA Desktop

Each seller should be able to submit a

response with pricing and comments.
The customer should receive a notification
from each of the sellers.
NA Desktop

The customer should be able to view

responses from each seller.
The responses should include detailed
pricing, terms, and any additional
comments. NA Desktop

Each seller should be able to approve or

reject the RFQ.
The customer should receive a notification
from each seller about the approval or NA Desktop
rejection.
Both sellers and customers should be able
to view a complete history of RFQs,
including the status, responses, and
actions taken

NA Desktop

A list of all cement orders is displayed,

including order ID, customer name, order
status, and date. NA Desktop

Only orders with the selected status should

be displayed.
NA Desktop

Order details should be displayed,

including items ordered, quantities,
delivery date, and customer information. NA Desktop

The specific order is displayed if it exists;

otherwise, a "No results found" message
appears.
NA Desktop

The order should be updated successfully,

and the new details should be reflected in
the order list.
NA Desktop

The order should be removed from the list,

and a success message should be
displayed. NA Desktop

Users should be able to see only the

options they are permitted to use (e.g.,
Admin can edit/delete orders, while a
regular user cannot). NA Desktop

Only orders within the specified date range

should be displayed.
NA Desktop
A file is downloaded in the chosen format
containing the order data.
NA Desktop

A list of all customer accounts should be

displayed, including customer ID, name,
email, etc. NA Desktop

The customer details page should display

the information such as name, email,
address, and phone number. NA Desktop

The customer details should be updated

successfully, and a confirmation message
should be displayed.
NA Desktop

A list of all orders placed by the customer

should be displayed, including order ID,
status, and date. NA Desktop

The new address should be added

successfully, and a confirmation message
should be displayed.
NA Desktop

The customer account should be deleted

successfully, and a success message
should be displayed. NA Desktop
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Medium

Medium

Medium
Medium

Medium

Medium

Medium

Medium

Medium

Medium

Medium
Medium

Low

High

Medium

Medium

Medium

Medium
Medium

High

High

High

High

High

High
High

High

High

Medium

High

High

High
Medium

High

High

High

High
Medium

Medium

Medium

Medium

High

High

High
High

High

High

High

High

High

High
High

High

Medium

High

High

High

High

High

High
High

High

High

High

High

High

High
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

Seller submits a new

SKU for approval
UT_SC_001 MC-77 Verify that Submitting
New SKU using
Standardized
Integration Template (CSV)

UT_SC_002 MC-77 Verify that Successful

Submission
Notification

System

UT_SC_003 MC-77 Verify that Submission

with Incomplete or
Incorrect Data

System

UT_SC_004 MC-77 Verify that Upload

Failure Due to File
Format Issues

System
UT_SC_005 MC-77 Verify that System
Error During
Submission
System

Admin reviews and

approves/rejects new
SKU
UT_SC_006 MC-78 Verify that SKU
Approval Notification
System

UT_SC_007 MC-78 Verify that SKU

Rejection Notification
with Reasons
Integration

UT_SC_008 MC-78 Verify that Notification

Not Sent

System

UT_SC_009 MC-78 Verify that Notification

Delivery Delay

System

UT_SC_010 MC-78 Verify that Notification

Delivery Delay due to
network issue.
System

Edit and Resubmit

Rejected SKU
UT_SC_011 MC-79 Verify that Edit
Rejected SKU

System
UT_SC_012 MC-79 Verify that Resubmit
Corrected SKU

System

UT_SC_013 MC-79 Verify that Incomplete

Resubmission

Integration

UT_SC_014 MC-79 Verify that Incomplete

Resubmission request
for SKU.

System

UT_SC_015 MC-79 Verify that

Resubmission After
Deadline

Integration

UT_SC_016 MC-79 Verify that Multiple

Rejections

Integration

Seller accesses
master catalog after
approval
UT_SC_017 MC-80 Verify that View
Approved SKUs.
Integration
UT_SC_018 MC-80 Verify that Search and
Filter SKUs
Integration

UT_SC_019 MC-80 Verify that system

should view relevant
SKUs.
System

UT_SC_020 MC-80 Verify that SKU Not

Available in Catalog
Integration

UT_SC_021 MC-80 Verify that system can

display message the
SKU is unavailable or
System pending.

UT_SC_022 MC-80 Verify that Catalog

System Error
System
 Total No. Of Test Cases : 22
High
Complexity Count :
1
Test Cases Prepared By : Chintha Sreekanth
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Seller login the seller panel. Seller can login and download the
2. Select download the standardized product standardized product template
template (CSV). (CSV)
3. Seller fill the required details.
4. Seller submit the file for catelog addition.

1. Seller login the seller panel. Seller receive a confirmation

2. Select download the standardized product message for submitted the new
template (CSV). SKU details.
3. Seller fill the required details.
4. Seller submit the file for catelog addition.
5.Seller received the conformation message.

1. Seller login the seller panel. Seller submit the file for catelog
2. Select download the standardized product addition with invalid data in CSV
template (CSV). file.
3. Seller not fill the required details or invalid
data.
4. Seller submit the file for catelog addition.

1. Seller login the seller panel. Seller upload a file that is not in
2. Select download the standardized product the standardized CSV.
template (CSV).
3. Seller not fill the required details or invalid
data and try to upload a file is not in the
standardized CSV.
4. Seller submit the file for catelog addition.
1. Seller login the seller panel. Seller can download the
2. Select download the standardized product standardized product template
template (CSV). (CSV) and fill the required details,
3. Seller fill the required details. Seller submit the file for catelog
4. Seller submit the file for catelog addition. addition.

1. Admin can login the Magento. Admin give the approval for
2. Admin check the catelog request. product SKU.
3. Admin review the product catelog.
4. Admin give the approval for the SKU.
5. System should send the notification to the
seller.
1. Admin can login the Magento. Admin reject approval for product
2. Admin check the catelog request. SKU.
3. Admin review the product catelog.
4. Admin not give the approval for the SKU.
5. System should send the notification to the
seller.

1. Admin can login the Magento. Admin can give approval or

2. Admin check the catelog request. rejected for product SKU.
3. Admin review the product catelog.
4. Admin give the approval or rejected for the
SKU.
5. System should send the notification to the
seller.
1. Admin can login the Magento. Admin can give approval or
2. Admin check the catelog request. rejected for product SKU.
3. Admin review the product catelog.
4. Admin give the approval or rejected for the
SKU.
5. System should send the notification to the
seller.
1. Admin can login the Magento. Admin can give approval or
2. Admin check the catelog request. rejected for product SKU.
3. Admin review the product catelog.
4. Admin give the approval or rejected for the
SKU.
5. System should send the notification to the
seller.

1. Seller login the seller panel. Seller can login and check the
2. Select check the received notification. notification.
3. Seller open the rejection notification.
4. Seller can see the reasons for the
rejection.
5.Seller have the option to edit the SKU
details.
1. Seller login the seller panel. Seller can edit the rejected SKU
2. Select check the received notification. and resubmit the corrected.
3. Seller open the rejection notification.
4. Seller can see the reasons for the
rejection.
5.Seller have the option to edit the SKU
details.
1. Seller login the seller panel. Seller fill the fields and leave the
2. Select check the received notification. mandatory fields.
3. Seller open the rejection notification.
4. Seller can see the reasons for the
rejection.
5.Seller have the option to edit the SKU
details.
6.Seller fill the fields and leave the
mandatory fields.

1. Seller login the seller panel. Seller fill the fields and leave the
2. Select check the received notification. mandatory fields and resubmitted.
3. Seller open the rejection notification.
4. Seller can see the reasons for the
rejection.
5. Seller have the option to edit the SKU
details.
6. Seller edit the SKU details and
resubmitted.

1. Seller login the seller panel. Seller can resubmit the SKU after a
2. Select check the received notification. specified deadline.
3. Seller open the rejection notification.
4. Seller can see the reasons for the
rejection.
5. Seller have the option to edit the SKU
details.
6. Seller edit the SKU details and
resubmitted.

1. Seller login the seller panel. Seller can resubmit the SKU
2. Select check the received notification. unresolved issues.
3. Seller open the rejection notification.
4. Seller can see the reasons for the
rejection.
5. Seller have the option to edit the SKU
details.
6. Seller edit the SKU details and
resubmitted.

1. Seller login to the seller panel. Seller can see the all approved
2. Select select the master catalog. SKU's.
3. Seller can view all approved SKUs.
4. Seller can add to the catelog.
1. Seller login to the seller panel. Seller can search with SKU using
2. Select select the master catalog. with filter option.
3. Seller can view all approved SKUs.
4. Seller can search with SKU's using with
filter.

1. Seller login to the seller panel. Seller can search with SKU using
2. Select select the master catalog. with filter option.
3. Seller can view all approved SKUs.
4. Seller can search with SKU's using with
filter.
5. System should view the relevant SKUs.
1. Seller login to the seller panel. Seller can search with not
2. Select select the master catalog. available SKU using with filter
3. Seller can view all approved SKUs. option.
4. Seller can search with not available SKU's
using with filter.

1. Seller login to the seller panel. Seller can search with not
2. Select select the master catalog. available SKU using with filter
3. Seller can view all approved SKUs. option.
4. Seller can search with not available SKU's
using with filter.

1. Seller login to the seller panel. Seller can try to access the master
2. Select select the master catalog. catalog.
3. Seller can view all approved SKUs.
4. Seller can search with available SKU's
using with filter.
 Medium Low
13 8

Test Device (for

Expected Results Test Data
mobile)

Verify that seller can download the NA Desktop

standardized product template (CSV) and
seller should be able to fill in all the
required product details, submit the file for
catalog addition.

Verify that seller can download the NA Desktop

standardized product template (CSV) and
seller should be able to fill in all the
required product details, submit the file for
catalog addition.

Verify that seller attempt to submit the NA Desktop

CSV file with missing or incorrect
mandatory details (e.g., missing SKU,
incorrect price format),then system should
reject the submission and display an error
message indicating the required
corrections.

Verify that seller try to upload a file that is NA Desktop

not in the standardized CSV format, then
system should reject the submission and
prompt me to use the correct template
format.
Verify that seller submitting a new SKU,if NA Desktop
system get error (e.g., server downtime or
network issue),then system should display
an error message and allow me to resubmit
after the issue is resolved.

Verify that admin has given approved the NA Desktop

SKU,then system should send a notification
to the seller informing them that the SKU
has been added to the master catalog.

Verify that admin has rejected the NA Desktop

SKU,then system should send a notification
to the seller with detailed reasons for the
rejection and steps to resubmit.

Verify that admin has approved or rejected NA Desktop

the SKU,then system fails to send a
notification, then the seller should not be
able to proceed with selling the product
and the system should log the error for the
admin to review.

Verify that admin has approved or rejected NA Desktop

the SKU,then system is a delay to sending
the notification due to external factors
(e.g., network issues),

Verify that system should display an in-app NA Desktop

notification when the seller next logs in,
ensuring they are aware of the SKU's
status.

Verify that seller has received a rejection NA Desktop

notification, when seller open the rejected
SKU,then seller should be able to view the
reasons for rejection and have the option
to edit the SKU details.
Verify that seller has edited the rejected NA Desktop
SKU and resubmit the corrected SKU,then
system should accept the SKU for review
again and notify me that it is under review.

Verify that seller resubmitting a rejected NA Desktop

SKU,When seller fail to correct the issues
outlined by the admin or leave mandatory
fields blank.

Verify that system should prevent the NA Desktop

resubmission and display an error message
indicating which fields need attention.

Verify that seller received a rejection NA Desktop

notice, seller attempt to resubmit the SKU
after a specified deadline (if any), then
system should prevent the resubmission
and display a message stating the SKU can
no longer be updated.

Verify that seller resubmits the SKU with NA Desktop

unresolved issues, then system should
escalate the review process to a different
admin for further assessment and notify
the seller accordingly.

Verify that seller access the master catalog NA Desktop

and seller should be able to view all SKUs
that have been approved and added to the
catalog.
Verify that seller given SKU has been NA Desktop
added to the master catalog, When seller
search or filter the catalog by product
category, name, or price.

Verify that system should display relevant NA Desktop

SKUs based on my search criteria.

Verify that seller searching the master NA Desktop

catalog,if a specific SKU is not available
(due to admin rejection or pending
approval).

Verify that system should notify me that NA Desktop

the SKU is unavailable or pending approval.

Verify that if system is under maintenance NA Desktop

or facing technical issues, seller try to
access the master catalog, system should
display a message informing me of the
downtime and estimated resolution time.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Medium

Medium
Medium

Medium

Medium

Medium

Low

Low

Medium
Medium

Low

Medium

Low

Low

Low
Medium

High

Medium

Low

Low
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

Enable RFQ Button

for High-Value
Carts
UT_RM_001 MC-83

Verify that RFQ Button

Integration Enabled for High-
Value Cart

UT_RM_002 MC-83

Verify that RFQ Button

Integration Disabled for Low-
Value Cart

UT_RM_003 MC-83

Verify that Incorrect

System
Threshold Application
UT_RM_004 MC-83

Verify that Threshold

Integration
Change Mid-Session

UT_RM_005 MC-83

Verify that new

Integration Threshold created
Mid-Session

Submit RFQ Form

UT_RM_006 MC-84

Verify that Access

Integration
RFQ Form

UT_RM_007 MC-84

Verify that Successful

Integration
RFQ Form Submission
UT_RM_008 MC-84

Verify that Incomplete

Integration
RFQ Form Submission

UT_RM_009 MC-84

Verify that Cart Not

Integration Cleared After
Submission

UT_RM_010 MC-84

Verify that RFQ

Integration Submission Failure
Due to System Error

Admin Assigns
Sellers to RFQ
UT_RM_011 MC-85
Verify that Admin
Integration Reviews RFQ and
Assigns Sellers

UT_RM_012 MC-85
Verify that admin can
Integration check the available
Seller Assignment

UT_RM_013 MC-85
Verify that Single
Integration
Seller Assignment
UT_RM_014 MC-85
Verify that Admin
System review and check
available sellers.

UT_RM_015 MC-85
Verify that Multi-Seller
Integration
Assignment.

UT_RM_016 MC-85

Verify that No Sellers

System
Available for RFQ

UT_RM_017 MC-85

Verify that Partial

Integration Seller Assignment for
RFQ

Seller Submits
Prices for RFQ
UT_RM_018 MC-86
Verify that Seller-
Specific RFQ Workflow
Integration
Seller’s
Role

UT_RM_019 MC-86
Verify that Seller
Integration Submits Updated
Prices

UT_RM_020 MC-86

Verify that Admin

Integration Reviews and
Compares Prices

UT_RM_021 MC-86

Verify that Incomplete

System Price Submission by
Seller
UT_RM_022 MC-86
Verify that Seller Price
System
Submission Error

Buyer Receives
Notification of
Updated Quote
UT_RM_023 MC-87
Verify that buyer
Integration Notification of
Updated Price

UT_RM_024 MC-87

Notification Not Sent

System
to Buyer

UT_RM_025 MC-87

System Delayed Notification

 Total No. Of Test Cases : 25
High
Complexity Count :
0
Test Cases Prepared By : Chintha Sreekanth
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Open browser and enter URL. Buyer want to see the "RFQ" button
2. Home page should display with/without enabled when my cart value exceeds
login. ₹1 lakh so that I can request a
3. Select the categories products and quotation for high-value orders.
navigate to the PLP page.
4. Select the RMA products and navigate to
the PDP page.
5. Add the RMC product into cart.

1. Open browser and enter URL. Buyer should not be see the "RFQ"
2. Home page should display with/without button,when my cart value not
login. exceeds ₹1 lakh so that buyer should
3. Select the categories products and not request a quotation for high-value
navigate to the PLP page. orders.
4. Select the RMA products and navigate to
the PDP page.
5. Add the ₹1 lack worth RMC product into
cart.

1. Open browser and enter URL. Buyer can see the "RFQ" button,when
2. Home page should display with/without cart value not exceeds ₹1 lakh.
login.
3. Select the categories products and
navigate to the PLP page.
4. Select the RMC products and navigate to
the PDP page.
1. Open browser and enter URL. Buyer cart value exceeds ₹1 lakh so
2. Home page should display with/without that buyer can request a quotation for
login. high-value orders.
3. Select the categories products and
navigate to the PLP page.
4. Select the RMA products and navigate to
the PDP page.
5. Add ₹1 lack worth RMC product into cart.

1. Open browser and enter URL. Buyer want to see the another "RFQ"
2. Home page should display with/without button enabled when my cart value
login. exceeds ₹2 lakh.
3. Select the categories products and
navigate to the PLP page.
4. Select the RMA products and navigate to
the PDP page.
5. Add more then ₹2 lack worth RMC product
into cart.

1. Open browser and enter URL.

2. Home page should display with/without
login.
3. Select the categories products and
navigate to the PLP page. Buyer added ₹1 lack worth RMC
4. Select the RMA products and navigate to product and click on RFQ button.
the PDP page.
5. Add ₹1 lack worth RMC product into cart.
6.Click on RFQ button.

1. Open browser and enter URL.

2. Home page should display with/without
login.
3. Select the categories products and
navigate to the PLP page.
4. Select the RMA products and navigate to Buyer should fill the RFQ form and
the PDP page. submitted.
5. Add ₹1 lack worth RMC product into cart.
6.Click on RFQ button.
7.Fill the RFQ form and submitted.
1. Open browser and enter URL.
2. Home page should display with/without
login.
3. Select the categories products and
navigate to the PLP page. Buyer should fill the RFQ form with
4. Select the RMA products and navigate to invalid and empty fields, should not
the PDP page. allow.
5. Add ₹1 lack worth RMC product into cart.
6.Click on RFQ button.
7.Fill the RFQ form and submitted.

1. Open browser and enter URL.

2. Home page should display with/without
login.
3. Select the categories products and
navigate to the PLP page.
4. Select the RMA products and navigate to Buyer should fill the RFQ form and
the PDP page. submitted.
5. Add ₹1 lack worth RMC product into cart.
6.Click on RFQ button.
7.Fill the RFQ form and submitted.

1. Open browser and enter URL.

2. Home page should display with/without
login.
3. Select the categories products and
navigate to the PLP page. Buyer should fill the RFQ form with
4. Select the RMA products and navigate to invalid and empty fields, should not
the PDP page. allow and throw error message
5. Add ₹1 lack worth RMC product into cart.
6.Click on RFQ button.
7.Fill the RFQ form and submitted.

1. Admin can login the Magento.

2. Admin check the RFQ request.
3. Admin review the RFQ. Admin review the RFQ requests from
buyer.

1. Admin can login the Magento.

2. Admin check the RFQ request.
3. Admin review the RFQ. Admin check the available seller.
4. Admin check the available seller.

1. Admin can login the Magento.

2. Admin check the RFQ request.
3. Admin review the RFQ. Admin assign to single seller.
4. Admin check the available seller.
5.Admin assign to the single seller.
1. Admin can login the Magento.
2. Admin check the RFQ request.
3. Admin review the RFQ. Admin review and check the available
4. Admin check the available seller. sellers.

1. Admin can login the Magento.

2. Admin check the RFQ request.
3. Admin review the RFQ. Admin assign to multiple seller.
4. Admin check the available seller.
5. Admin assign to the multiple seller.
1. Admin can login the Magento.
2. Admin check the RFQ request.
3. Admin review the RFQ. Admin could not assign to seller.
4. Admin check the available seller. Based on non availability.

1. Admin can login the Magento.

2. Admin check the RFQ request.
3. Admin review the RFQ.
4. Admin check the available seller. Admin assign to available sellers.
5. Admin assign to the available sellers.

1. Seller login the seller panel.

2. Check the RFQ request.
3. Seller update the prices. Buyer has filled the RFQ form and
submitted successfully and navigate
to the checkout page.

1. Seller login the seller panel. Seller should received the buyer RFQ
2. Check the RFQ request. request.
3. Seller update the prices.

1. Seller login the seller panel. Admin review the multiple seller
2. Check the RFQ request. prices.
3. Seller update the prices and submitted.
4.Admin login the Magento and review the
RFQ request.

1. Seller login the seller panel. Seller should include the mandatory
2. Check the RFQ request. details for RFQ.
3. Seller update the prices and submitted.
1. Seller login the seller panel. Seller should include the mandatory
2. Check the RFQ request. details for RFQ.
3. Seller update the prices and submitted.

1. Admin can login the Magento. Admin can select the best price for
2. Admin check the RFQ request. quote is update.
3. Admin review the RFQ.
4. Admin assign select the best prices for
quote is update.
1. Admin can login the Magento. Admin can select the best price for
2. Admin check the RFQ request. quote is update.
3. Admin review the RFQ.
4. Admin assign select the best prices for
quote is update.
1. Admin can login the Magento. Admin can select the best price for
2. Admin check the RFQ request. quote is update.
3. Admin review the RFQ.
4. Admin assign select the best prices for
quote is update.
 Medium Low
18 7

Test Device (for

Expected Results Test Data
mobile)

Verify that buyer adds products to the cart, NA Desktop

the total cart value exceeds ₹1 lakh,then
the "RFQ" button should be enabled and
visible to the buyer next to the "Buy Now"
button.

Verify that buyer adds products to the cart, NA Desktop

the total cart value is below ₹1 lakh,then
the "RFQ" button should remain disabled
and only the "Buy Now" button should be
visible.

Verify that buyer has added products worth NA Desktop

less than ₹1 lakh, (it can be configurable),if
the system mistakenly enables the "RFQ"
button,then system should correct the
issue and disable the "RFQ" button until
the correct threshold is met.
Verify that buyer is browsing the NA Desktop
marketplace,the system updates the cart
threshold value for RFQ while the buyer is
adding more items to the cart.

Verify that buyer is adding more items to NA Desktop

the cart,the system should immediately
reflect the new threshold without any
disruption to the buyer's session.

Desktop

Verify that buyer’s cart value exceeds ₹1

lakh,then buyer clicks the "RFQ" button,
NA
then system should display the RFQ form
for the buyer to fill out.

Desktop

Verify that buyer has filled and submits in

the RFQ form, then system should accept
the submission, clear the cart, and display NA
a confirmation message that the RFQ has
been successfully submitted.
 Desktop

Verify that buyer attempts to submit the

RFQ form with missing any mandatory
fields, then the system should display an NA
error message indicating the required
fields that need to be filled.

Desktop

Verify that buyer has filled and submits in

the RFQ form successfully, then system
should automatically clear the cart, and if NA
the cart remains filled, it should trigger an
error for correction.

Desktop

Verify that system experiences an error

during RFQ form submission, then system
should display a message indicating the
NA
error, once error has resolved allow the
buyer to resubmit the form without losing
data.

Verify that buyer has submitted an Desktop

RFQ,admin should reviews the RFQ
request, system should allow the admin to NA
assign one or more sellers based on the
products and their availability.
Desktop
Verify that admin is assigning a seller to
NA
the RFQ.

Desktop
Verify that if only one seller can fulfil the
complete order, then system should allow
NA
the admin to assign the RFQ to that single
seller.
 Desktop
Verify that admin is reviewing an RFQ and
NA
check the available sellers.

Desktop
Verify that multiple sellers are required to
fulfil the order, system should allow the NA
admin to assign the RFQ to multiple sellers.

Desktop
Verify that admin is reviewing an RFQ,if no
sellers are available to fulfil the order, then
system should notify the admin that no NA
suitable sellers can be assigned, and the
buyer should be notified accordingly.

Desktop
Verify that RFQ requires for multiple
products, only a portion of the order can be
fulfilled by available sellers, system should
NA
allow the admin to assign partial orders to
sellers and notify the buyer of the partial
fulfilment.

Verify that for RFQ, the seller will have the NA Desktop
functionality to convert the RFQ inquiry
into an order/cart with a click of a button
after updating the prices. The buyer can
then proceed to checkout from the
frontend as usual.
Verify that once seller has received an NA Desktop
RFQ,seller updates the prices and shipping
charges, system should allow the seller to
submit the updated information to the
admin for review.
Verify that seller has submitted the prices, NA Desktop
the admin reviews the submissions from
multiple sellers, the system should display
the prices and shipping costs for the admin
to compare and choose the most suitable
seller.

Verify that seller is submitting prices for an NA Desktop

RFQ,if seller forgets to include mandatory
details such as shipping charges, then
system should prevent submission and
display an error message prompting the
seller to complete the missing information.
Verify that seller is submitting prices, the NA Desktop
system get an error during submission,
system should notify the seller of the error
and allow them to retry the submission.

Verify that admin has selected the best NA Desktop

price, the quote is updated in the "All
Orders" section.

Verify that admin has updated the RFQ NA Desktop

price, system fails to send the notification
to the buyer, system should log the error
and alert the admin to resolve the issue.

Verify that admin has updated the price, NA Desktop

system delays sending the notification to
the buyer.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Low
 Low

Low

Medium

Medium
Medium

Medium

Medium

Medium

Medium

Medium
 Low

Medium

Medium

Medium

Medium

Medium

Low

Medium
Medium

Medium

Low

Low
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

Invoice Generation on
Shipment Readiness

UT_IM_001 Verify that Invoice

Generation upon
Integration MC-56 Shipment Readiness

UT_IM_002 Verify that invoice has

required details.
Integration MC-56

UT_IM_003 Verify that Attempt to

Generate Invoice
Integration MC-56 before Shipment
Readiness

UT_IM_004 Verify that invoice

generated once the
Integration MC-56 shipment is ready for
dispatch.

UT_IM_005 Verify that Invoice

Generation for
System MC-56 Cancelled or Returned
Orders

UT_IM_006 Verify that Invoice not

generated.
System MC-56
 Separate Invoices for
Orders from Different
Sellers
UT_IM_007 Verify that Separate
Invoices for Each
Integration MC-57 Seller

UT_IM_008 Verify that system

should generate
System MC-57 separate invoice.

UT_IM_009 Verify that Single

Invoice for Multiple
System MC-57 Sellers

UT_IM_010 Verify that Single

Invoice not generate
System MC-57 for Multiple Sellers

UT_IM_011 Verify that Single

Seller Order
System MC-57

HSN Code in Product

Invoices
UT_IM_012 Verify that HSN Code
in Invoice
Integration MC-58

UT_IM_013 Verify that Missing

HSN Code in Product
Integration MC-58 Details

UT_IM_014 Verify that hold the

invoice generation.
System MC-58

Invoice Data Flow to

SAP for Commission
Calculation
UT_IM_015 Verify that Successful
Data Flow to SAP
Integration MC-59

UT_IM_016 Verify that Successful

Data Flow to SAP
Integration MC-59

UT_IM_017 Verify that Failed Data

Sync with SAP
Integration MC-59

UT_IM_018 Verify that Data Sync

with SAP after issue
has resolved.
Integration MC-59

Invoicing for Multi-

Seller Orders
UT_IM_019 MC-217 Verify that Invoice
generate for Multi-
Integration Seller Orders

UT_IM_020 MC-217 Verify that Invoice

generated with
System required details.

UT_IM_021 MC-217 Verify that Invoice not

generate for Multi-
Seller Orders
System
 Total No. Of Test Cases : 21
High
Complexity Count :
0
Test Cases Prepared By : <tester>
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Open browser and enter URL. Buyer has placed the order.
2. Login with valid credentials.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Chintha Sreekanth
2. Login with valid credentials.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. buyer trying to view the invoice.
2. Login with valid credentials.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Invoice generated after shipment is
2. Login with valid credentials. ready for dispatch.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer can cancelled or return the
2. Login with valid credentials. order.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer can cancelled or return the
2. Login with valid credentials. order.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer placed the order from different
2. Login with valid credentials. seller products.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer placed the order from different
2. Login with valid credentials. seller products.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer add the items from multiple
2. Login with valid credentials. seller products.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer placed the order from multiple
2. Login with valid credentials. seller products.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer has placed the order from
2. Login with valid credentials. single seller products only.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.

1. Open browser and enter URL. Buyer has purchased the HSN Code
2. Login with valid credentials. product
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer has purchased the HSN Code
2. Login with valid credentials. product
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Buyer has purchased the HSN Code
2. Login with valid credentials. product
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Invoice has generated with required
2. Login with valid credentials. details.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Invoice has generated with required
2. Login with valid credentials. details.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
System send the data to the SAP.
1. Open browser and enter URL.
2. Login with valid credentials.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.

System send the data to the SAP.

1. Open browser and enter URL.
2. Login with valid credentials.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.

1. Open browser and enter URL. Buyer placed the an order with
2. Login with valid credentials. products from multiple sellers.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
1. Open browser and enter URL. Invoice generated based on multiple
2. Login with valid credentials. sellers.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
Buyer placed the an order with
1. Open browser and enter URL. products from multiple sellers.
2. Login with valid credentials.
3. Click on sales and invoice.
4. Select the orders and generated the
invoice.
 Medium Low
15 6

Test Device (for

Expected Results Test Data
mobile)

Verify that verify that buyer has placed an Desktop

order,the order is ready for dispatch then
the system should generate an invoice for NA
the order.

Verify that generate an invoice should Desktop

include details such as the order number,
product details, tax information, HSN code, NA
and total amount.

Verify that order is still being processed Desktop

buyer attempt to view or request an
invoice before the order is ready for NA
dispatch.

Verify that system should display a Desktop

message indicating that the invoice will
only be generated once the shipment is NA
ready for dispatch.

Verify that if buyer has been cancelled or Desktop

returned the order,then system processes
to cancellation/return the order. NA

Verify that buyer has been cancelled or Desktop

returned the order, system should no
invoice should be generated, and any NA
generated invoice should be marked as
void in the system.
Verify that buyer with items from multiple Desktop
sellers in my order, items are ready for
shipment. NA

Verify that system separate invoices Desktop

should be generated for each seller and
each invoice should contain the specific NA
order number and details related to the
respective seller’s products.
Verify that buyer with items from multiple Desktop
sellers, buyer proceed with the checkout
and the items are dispatched. NA

Verify that buyer should not receive a Desktop

single invoice combining all seller orders
and instead, buyer should receive NA
individual invoices per seller.

Verify that buyer placed the order from Desktop

single seller products only, items are ready
for shipment, system should generate only NA
one invoice for the entire order.

Verify that buyer has purchased the HSN NA Desktop

Code product, the HSN code of the product
should be included in the invoice for tax
compliance.

Verify that buyer has purchased the HSN NA Desktop

Code product, if HSN code is missing to the
product, system should not generate an
invoice without HSC Code.

Verify that system should throw an error NA Desktop

indicating the missing HSN code and
invoice generation should be paused until
the code is provided.
Verify that system invoice has been NA Desktop
generated for an order, invoice data is
processed, then the data should
automatically flow to the SAP system for
further calculations.
Verify that SAP system automatically NA Desktop
calculations for commission and related
processes should be executed based on
the data.

Verify that system invoice has been NA Desktop

generated for an order, system attempts to
send the data to SAP and there is a failure
(e.g., network issue or system error),then
system should notify the administrator of
the failure.
NA Desktop
Verify that ,system attempts to send the
data to SAP and there is a failure (e.g.,
network issue or system error),the data
should be queued for reprocessing once
the issue is resolved.

Verify that buyer places an order with NA Desktop

products from multiple sellers, the
products are ready for dispatch.

Verify that system should generated NA Desktop

separate invoices for each seller and each
invoice includes the order number, HSN
code, and applicable tax details.

Verify that system generates separate NA Desktop

invoices for multi-seller orders, if there is
an error in generating an invoice, system
alerts the buyer with a message stating,
"There was an issue generating your
invoice. Please contact support."
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Low

Low

Low

Low

Low
Medium

Medium

Medium

Medium

Low

Medium

Medium

Medium
Medium

Medium

Medium

Medium

Medium

Medium

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

Sellers Receive
Automated
Notifications for
Payment
Disbursement

Verify that Successful

notification upon
UT_PM_001 Integration MC-242
payment
disbursement.

Verify that seller

received notification
UT_PM_002 System MC-242 via
whatsapp,Email,and
SMS

Verify that No
notification sent due
UT_PM_003 System MC-242
to system failure.
 Verify that seller not
UT_PM_004 System MC-242 received the
notification.

Automatic
Commission
Recalculation After
Return or Refund
Verify that Successful
commission
UT_PM_005 Integration MC-243 recalculation after a
return

Verify that
automatically
UT_PM_006 Integration MC-243 commission adjusted.

Verify that
Commission
UT_PM_007 System MC-243 recalculation fails due
to incorrect rules.

Verify that system not

accepted return
UT_PM_008 System MC-243 request

Verify that Refund

occurs, triggering
UT_PM_009 Integration MC-243 automatic commission
recalculation.

Automated
Accounting
Adjustments for Tax
Deductions
MC-244 Verify that Tax
deductions adjusted
UT_PM_010 Integration after a return.

MC-244 Verify that update

invoice after a return.
UT_PM_011 System
 MC-244 Verify that Successful
adjustment of
commission and tax
UT_PM_012 System deductions after a
refund.

MC-244 Verify that seller

received the an
UT_PM_013 Integration updated statement.

MC-244 Verify that Incorrect

invoice correction
UT_PM_014 System after return outcome.

MC-244 Verify that No tax

deduction change for
UT_PM_015 System non-returnable items.

Sellers Receive
Detailed Statements
of Payment
Deductions
MC-245 Verify that System
generate the
UT_PM_016 Integration statement.

MC-245 Verify that Statement

includes detailed
UT_PM_017 System breakdown of
charges.
MC-245 Verify that Missing
details in payout
UT_PM_018 System statement.

MC-245 Verify that seller

commission
UT_PM_019 System recalculated due to
return or refund.
MC-245 Verify that
Commission changes
UT_PM_020 Integration reflected in the
payout statement.
 Total No. Of Test Cases : 20
High
Complexity Count :
4
Test Cases Prepared By : Chintha Sreekanth
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Open browser and enter URL.

2. Login with valid credentials.
3. Select the categories products and
navigate to the PLP page.
Buyer has completed the payment.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. Buyer has placed the order with payment.

1. Open browser and enter URL.

2. Login with valid credentials.
3. Select the categories products and
navigate to the PLP page. System send the notification to the
4. Select the products and navigate to the seller.
PDP page.
5. Add the product into cart.
6. Buyer has placed the order with payment.

1. Open browser and enter URL.

2. Login with valid credentials.
3. Select the categories products and
navigate to the PLP page. System not send the notification to
4. Select the products and navigate to the the seller.
PDP page.
5. Add the product into cart.
6. Buyer has placed the order with payment.
 Seller not received the notification.
1. Open browser and enter URL.
2. Login with valid credentials.
3. Select the categories products and
navigate to the PLP page.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. Buyer has placed the order with payment.

Buyer has raised the return request

1. Open browser and enter URL. for previous order.
2. Login with valid credentials.
3. Click on sales and return.

1. Open browser and enter URL. Buyer return request accepted.

2. Login with valid credentials.
3. Click on sales and return.

Buyer return request not accepted.

1. Open browser and enter URL.
2. Login with valid credentials.
3. Click on sales and return.

1. Open browser and enter URL. Buyer return request not accepted.
2. Login with valid credentials.
3. Click on sales and return.

Buyer got the refund amount.

1. Open browser and enter URL.
2. Login with valid credentials.
3. Click on sales and return.

1. Open browser and enter URL. Buyer has raised the return request
2. Login with valid credentials. for previous order.
3. Click on sales and return.
4. Select the previous order and raised the
return request.
1. Open browser and enter URL. System accept return request and
2. Login with valid credentials. calculate the refund amount.
3. Click on sales and return.
4. Select the previous order and raised the
return request.
 System adjust the tax deductions.
1. Open browser and enter URL.
2. Login with valid credentials.
3. Click on sales and return.
4. Select the previous order and raised the
return request.

1. Open browser and enter URL. Refund has processed successfully.

2. Login with valid credentials.
3. Click on sales and return.
4. Select the previous order and raised the
return request.
1. Open browser and enter URL. Buyer return request accepted.
2. Login with valid credentials.
3. Click on sales and return.
4. Select the previous order and raised the
return request.
1. Open browser and enter URL. Buyer has raised a return request
2. Login with valid credentials. non-returnable products.
3. Click on sales and return.
4. Select the previous order and raised the
return request.

1. Open browser and enter URL. Seller payout has processed.

2. Login with valid credentials.
3. Click on sales and order.
4. Select the previous order and details.
1. Open browser and enter URL. Seller can see the statement and
2. Login with valid credentials. download.
3. Click on sales and order.
4. Select the previous order and details.
Seller statement should has required
1. Open browser and enter URL. data.
2. Login with valid credentials.
3. Click on sales and order.
4. Select the previous order and details.

1. Open browser and enter URL. Seller commission recalculate.

2. Login with valid credentials.
3. Click on sales and order.
4. Select the previous order and details.
1. Open browser and enter URL. Seller commission and charges
2. Login with valid credentials. calculate.
3. Click on sales and order.
4. Select the previous order and details.
 Medium Low
12 4

Test Device (for

Expected Results Test Data
mobile)

Verify that once payout has been

processed, system system generates a NA Desktop
payment confirmation.

Verify that seller should receive

notifications via WhatsApp, Email, and SMS
and the notification should include detailed NA Desktop
statements of tax deductions and other
applicable charges.

Verify that payout has been processed, if

there is a system issue in generating the
notification.

NA Desktop
Verify that seller should not receive any
notification and the system should log the
issue for further investigation.

NA Desktop

Verify that buyer has raised the return NA

request and it's processed. System
recalculates the commission based on Desktop
predefined rules.

Verify that return request processed. NA

Seller's commission and payout should be
adjusted automatically. Desktop

Verify that once return request processed, NA

the commission recalculation logic fails due
to incorrect or missing rules Desktop

Verify that system should prevent payout NA

processing and it should notify the admin
to rectify the rules. Desktop

Verify that refund has been issued, system NA

recalculates the commission and adjusts
the payout. Seller's payout should reflect Desktop
the correct amount after the refund.

Verify that return has been processed, NA

system recalculates the seller's payout.
Desktop

Verify that Magento should adjust tax NA

deductions accordingly and provide an
updated invoice. Desktop
Verify that refund has been processed, NA
system adjusts commissions and tax
deductions.
Desktop

Verify that seller should receive an NA

updated statement showing the adjusted
payout and tax amounts. Desktop

Verify that return has been processed, the NA

invoice correction fails due to incorrect
data entry. System should flag the error Desktop
and notify the admin for manual correction.

Verify that non-returnable item has been NA

sold, refund is requested but not
processed. Then no adjustments should be Desktop
made to the seller’s tax deductions or
payout.

Verify that seller payout has been NA

processed, system generates the
statement for the seller. Desktop

Verify that the statement should include a NA

detailed breakdown of taxes, commissions,
and other charges applied. Desktop

Verify that Seller payout has been NA

processed. The seller views the statement.
If any details are missing, the system Desktop
should notify the seller to contact support
for clarification.
Verify that seller commission has been NA
recalculated due to a return or refund.
Desktop

Verify that seller views their payout NA

statement and updated commission should
be clearly indicated along with the reason Desktop
for the change.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Low

Low
 Low

Low

Medium

Medium

Medium

Medium

Medium

High
 High

High

Medium

Medium

Medium

Medium

High

Medium

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of T

Complex

Test Cases Pre

Test Cases Exe
Test Env

Test Case # Test Case Type Covered ID's Test Case Description

Display "Starting From"

Price on PLP and Home
Page

Verify that Display

UT_PM_001 Integration MC-323 "Starting From" Price on
PLP and Home Page

Verify that product

UT_PM_002 Integration MC-323 prices display from
Home page to PLP.

Verify that User enter

UT_PM_003 Integration MC-323
the Pin Code.

Verify that Display

UT_PM_004 System MC-323 "Starting From" Price
Based on Pin code

Display Seller-Specific
Prices on PDP
MC-324
Verify that User see the
UT_PM_005 Integration products on Home Page
and PLP.
 MC-324

Verify that Display

UT_PM_006 Integration Seller-Specific Prices on
PDP

MC-324 Verify that User see the

same product from
multiple sellers.
UT_PM_007 Integration

MC-324 Verify that Allow User to

Select Seller on PDP.

UT_PM_008 Integration

Centralized Price
Control for Sellers and
Admins
MC-325 Verify that Real-Time
Price Control for Sellers

UT_PM_009 Integration

MC-325 Verify that Admin can

access product pricing.
UT_PM_010 System

MC-325 Verify that Real-Time

Price Control for Admins
UT_PM_011 System

Automated Price
Approval Workflow and
Threshold Validation
 Verify that Price
Threshold Validation for
Sellers
UT_PM_012 Integration MC-326

Verify that Price

Threshold Validation for
Sellers

UT_PM_013 Integration MC-326

Verify that Seller update

the update the
threshold price.

UT_PM_014 System MC-326

Verify that Automated

Price Approval Workflow
for Admins

UT_PM_015 System MC-326

Dynamic MoP-Based
Pricing and Suggestions

MC-327 Verify that Dynamic

Price Based on Pickup
Store Pin code

UT_PM_016 Integration
 MC-327 Verify that Seller
Overrides Suggested
Price

UT_PM_017 Integration

MC-327 Verify that Seller

Overrides Suggested
Price

UT_PM_018 Integration

MC-327 Verify that Seller

Overrides based on
price range.

UT_PM_019 System

Product Variant Pricing

Management
MC-328 Verify that Define
Variant-Specific Prices
UT_PM_020 Integration

MC-328 Verify that

UT_PM_021 Integration

MC-328 Verify that Display

Variant Prices on PDP

UT_PM_022 Integration
 MC-328 Verify that

UT_PM_023 System

Price Override and

Manual Validation by
Admin
Verify that Admin
Manually Overrides
Price
UT_PM_024 Integration MC-329

Verify that Price

Validation by Admin
UT_PM_025 Integration MC-329

Verify that Admin can

review the prices.
UT_PM_026 System MC-329
 Total No. Of Test Cases : 26
High
Complexity Count :
1
Test Cases Prepared By : Chintha Sreekanth
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Open browser and enter URL and hit.

2. User navigate to the Home Page.
User has navigate to the Home page
3. Select the categories products and
or PLP.
navigate to the PLP page.

1. Open browser and enter URL and hit.

2. User navigate to the Home Page.
User has navigate to the Home page
3. Select the categories products and
or PLP.
navigate to the PLP page.

1. Open browser and enter URL and hit. User enter the PIN Code.
2. User navigate to the Home Page.
3. Select the categories products and
navigate to the PLP page.

1. Open browser and enter URL and hit. Based on pin code lowest prices
2. User navigate to the Home Page. products display on the Page.
3. Select the categories products and
navigate to the PLP page.

Buyer has navigate to the home page

1. Open browser and enter URL and hit. or PLP.
2. User navigate to the Home Page.
3. Select the categories products and
navigate to the PLP page.
4.Select the product and navigate to the PDP.
 Buyer enter the Pin Code and see the
1. Open browser and enter URL and hit. lowest price products.
2. User navigate to the Home Page. 3.
User enter the Pin Code.
4. Select the categories products and
navigate to the PLP page.
5.Select the product and navigate to the PDP.

Buyer enter the Pin Code and see the

1. Open browser and enter URL and hit. lowest price products in PLP.
2. User navigate to the Home Page. 3.
User enter the Pin Code.
4. Select the categories products and
navigate to the PLP page.
5.Select the product and navigate to the PDP.

Buyer can see multiple sellers

1. Open browser and enter URL and hit. products.
2. User navigate to the Home Page. 3.
User enter the Pin Code.
4. Select the categories products and
navigate to the PLP page.
5.Select the product and navigate to the PDP.

1. Open browser and enter URL and hit. Seller login to seller panel and update
2. Seller navigate to the Home Page. 3. the prices.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
1. Open browser and enter URL and hit. Admin login to the Magento and
2. Admin navigate to the Home Page. update the prices.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
1. Open browser and enter URL and hit. Admin login to the Magento and
2. Admin navigate to the Home Page. control the prices.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
1. Open browser and enter URL and hit. Seller login to seller panel and update
2. Seller navigate to the Home Page. 3. the prices.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.

1. Open browser and enter URL and hit. Seller login to seller panel and giving
2. Seller navigate to the Home Page. 3. the price more then price range.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
price.

1. Open browser and enter URL and hit. Seller giving the price more then
2. Seller navigate to the Home Page. 3. threshold price range.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
price.

1. Open browser and enter URL and hit. Seller giving the price more then
2. Seller navigate to the Home Page. 3. threshold price range.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
threshold price.

1. Open browser and enter URL and hit. Seller map the store's pin code.
2. Seller navigate to the Home Page. 3.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
threshold price.
1. Open browser and enter URL and hit. Seller update the product price range
2. Seller navigate to the Home Page. 3. based on Mop.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
threshold price.

1. Open browser and enter URL and hit. Seller override the price based on
2. Seller navigate to the Home Page. 3. suggested price.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
threshold price.

1. Open browser and enter URL and hit. System allow to the override the
2. Seller navigate to the Home Page. 3. price.
Seller select the Registered Sellers
4. Seller login with valid details.
5. Seller navigate to the dashboard. 6.
Seller click on catelog management and
select the Manage price.
7. Seller select the product and update the
threshold price.

1. Open browser and enter URL and hit. Admin can update the price
2. Admin navigate to the Home Page.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
1. Open browser and enter URL and hit. Admin can change the price based
2. Admin navigate to the Home Page. product variants.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
User can see the products prices
1. Open browser and enter URL and hit. based on variants.
2. User navigate to the Home Page. 3.
User enter the Pin Code.
4. Select the categories products and
navigate to the PLP page.
5.Select the product and navigate to the PDP.
 User can see the products prices
1. Open browser and enter URL and hit. based on variants.
2. User navigate to the Home Page. 3.
User enter the Pin Code.
4. Select the categories products and
navigate to the PLP page.
5.Select the product and navigate to the PDP.

1. Open browser and enter URL and hit. Admin can change the price based
2. Admin navigate to the Home Page. sellers.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
1. Open browser and enter URL and hit. Admin can review the seller update
2. Admin navigate to the Home Page. the prices.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
1. Open browser and enter URL and hit. Admin can approve or reject the
2. Admin navigate to the Home Page. seller product prices.
3. Admin login with valid details.
4. Admin navigate to the dashboard. 6.
Click on Market place menu and select the
manage prices.
 Medium Low
25 0

Test Device (for

Expected Results Test Data
mobile)

Verify that user browsing the PLP or Home

Page, products are displayed, the platform
NA Desktop
should show the "Starting From" price for
each product.

Verify that products represents the lowest Desktop

price available across all sellers for the
user's selected Pin code and this price
must be pulled from the master catalog, NA
considering the SKU with the lowest range
as defined by Utec.

Verify that user navigate to the home page Desktop

or PLP and entered a Pin code.
NA

Verify that the "Starting From" price should Desktop

reflect the lowest price for that specific Pin
code across all sellers and the price should NA
update dynamically if the user changes the
Pin code.

Verify that user clicks on a product from Desktop

the PLP or Home Page. User is redirected
to the PDP.
NA
Verify that the system should display Desktop
prices from different sellers for that
product and the platform should prioritize
and highlight the price from the most NA
relevant seller based on the seller
hierarchy rules.

Verify that user navigate on the PDP.user Desktop

see multiple sellers offer the same product.

NA

Verify that system should display a list of Desktop

sellers and their prices and he user should
be able to select their preferred seller from
the list. NA

Verify that seller is logged into the system Desktop

and seller view their product pricing. The
system should allow the seller to view and
update prices for their products in real- NA
time within the set thresholds.

Verify that admin is logged into the system Desktop

and access product pricing.
NA

Verify that system should allow the admin Desktop

to update pricing for products centrally
across the platform and any changes
made by the admin should reflect in real- NA
time across all serviceable Pin codes for
that product.
Verify that seller is updating prices for their Desktop
products. The seller attempts to enter a
price below or above the predefined range
in the master catalog. NA

Verify that the system should display an Desktop

error message stating that the price is
outside the allowed range and the system
should prevent the seller from saving the
price. NA

Verify that seller submits a price for Desktop

approval that is outside the price to
allowed threshold. System should detects
the price is outside the range.
NA

Verify that the system should automatically Desktop

trigger an approval workflow for the admin
and the admin should receive a notification
to approve or reject the price adjustment.
NA

Verify that seller is updating the price for a Desktop

product and seller inputs the pickup store's
Pin code.

NA
Verify that system should automatically Desktop
apply the price range for that SKU based
on the predefined MoP for the Pin code and
the seller should see a recommended price
based on the cost price NA

Verify that system displays a suggested Desktop

price for a product. Seller decides to set a
different price within the allowed range.

NA

Verify that the system should allow the Desktop

seller to override the suggested price and
save their preferred price.

NA

Verify that admin is setting prices for a Desktop

product and product has multiple variants
(e.g., different sizes or colors).
NA

Verify that system should allow the admin Desktop

to set unique prices for each variant based
on their attributes.
NA

Verify that user is viewing a product with Desktop

multiple variants. The user selects a
specific variant (e.g., a different size or
color). NA
Verify that system should display the Desktop
corresponding price for that variant
dynamically on the PDP.
NA

Verify that admin is reviewing pricing set Desktop

by a seller.admin determines that the price
needs to be adjusted. System should allow
the admin to manually override the price NA
and set a new price

Verify that seller submits a price for a Desktop

product. The price requires validation
based on platform rules.
NA

Verify that the system should route the Desktop

price for manual review by the admin and
admin should be able to approve or reject
the price before it becomes visible on the NA
platform.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Medium

Medium

Medium
Medium

Medium

Medium

Medium

Medium

Medium
Medium

Medium

High

Medium

Medium
Medium

Medium

Medium

Medium

Medium

Medium
Medium

Medium

Medium

Medium
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Total No. Of Tes

Complexit

Test Cases Prep

Test Cases Exec
Test Envir

Test Case
Test Case # Test Case Type Covered ID's
Description

Home Delivery - Post-

Order Cancellation
Period
UT_RA_001 MC-225 Verify that customer
cancel the order.

Integration

UT_RA_002 MC-225 Verify that customer

cancel the order
without any penalties.

Integration

UT_RA_003 MC-225 Verify that customer

cancel the order after
2 hours.

System
UT_RA_004 MC-225 Verify that customer
cancelled the order
and get the refund.

System

UT_RA_005 MC-225 Verify that customer

notification delay and
contact support team.

System

Home Delivery -
Refund/Complaint
Period
UT_RA_006 MC-227 Verify that customer
received the order.

System

UT_RA_007 MC-227 Verify that customer

raise the request for
refund or lodge.
Integration

UT_RA_008 MC-227 Verify that customer

contact to the support
team.
System

UT_RA_009 MC-227 Verify that system

fails to initiate the
complaint process.
System
UT_RA_010 MC-227 Verify that customer
support is alerted

System

Post-Order
Cancellation Period
(BOPIS & ROPIS)
UT_RA_011 MC-232 Verify that customer
cancel the order
within 2 hours.
System

UT_RA_012 MC-232 Verify that customer

can get full refund.

Integration

UT_RA_013 MC-232 Verify that customer

can not get full
refund.

Integration

UT_RA_014 MC-232 Verify that system not

accepted the cancel
request due to error.

Integration

Refund/Complaint
Period Initiation
UT_RA_015 MC-233 Verify that customer
found an issue to the
order.

Integration
UT_RA_016 MC-233 Verify that customer
get the ticket number
and notification.

Integration

UT_RA_017 MC-233 Verify that customer

raise the refund
request after 72 hour.

System

UT_RA_018 MC-233 Verify that system not

accepted the
refund/complaint
request due to error.
Integration

UT_RA_019 MC-233 Verify that system not

accepted the
refund/complaint due
to technical issues.
System

Post-Delivery Return
Request for Wrong or
Incomplete Item
MC-236 Verify that Return
request for incorrect
or incomplete item

UT_RA_020 Integration
 MC-236 Verify that Attempted
return outside the 72-
hour window.

UT_RA_021 Integration

MC-237 Post-Delivery Return

MC-238 Request for Damaged
Product
MC-238 Verify that Return
request for damaged
product.

UT_RA_022 Integration

Quality Complaint for

Delivered Item
MC-239 Verify that Quality
complaint within 30
days.

UT_RA_023 Integration

MC-239 Verify that Complaint

outside 30-day
window.

UT_RA_024 System

Enforcement of No
Return Policy
MC-240 Verify that No return
request allowed for
specific SKUs.

UT_RA_025 Integration
 MC-240 Verify that Return
request for valid
conditions (wrong
item, damaged,
quality issue).
UT_RA_026 Integration
 Total No. Of Test Cases : 26
High
Complexity Count :
7
Test Cases Prepared By : Chintha Sreekanth
Test Cases Executed By : <tester>
Test Environment :

Test Steps or Test Procedure Pre-condition (If any)

1. Open browser and enter URL. Customer has placed the order.
2. Login with valid credentials.
3. Select the categories products and
navigate to the PLP page.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. User has placed the order.
7. User can cancel the order.

1. Open browser and enter URL. Customer can cancelled the order
2. Login with valid credentials. within 2 hours.
3. Select the categories products and
navigate to the PLP page.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. User has placed the order.
7. User can cancel the order within 2 hours.

1. Open browser and enter URL. Customer can try to cancelled the
2. Login with valid credentials. order after 2 hours.
3. Select the categories products and
navigate to the PLP page.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. User has placed the order.
7. User can cancel the order after 2 hours.
1. Open browser and enter URL. Customer get the refund for order
2. Login with valid credentials. cancelation.
3. Select the categories products and
navigate to the PLP page.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. User has placed the order.
7. User can cancel the order within 2 hours.

1. Open browser and enter URL. Customer get the refund delay and
2. Login with valid credentials. notification.
3. Select the categories products and
navigate to the PLP page.
4. Select the products and navigate to the
PDP page.
5. Add the product into cart.
6. User has placed the order.
7. User can cancel the order within 2 hours.

1. Open browser and enter URL. customer raise request for refund or
2. Login with valid credentials. complaint within 72 hours.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Raise the request for refund or lodge.

1. Open browser and enter URL. customer received the ticket number.
2. Login with valid credentials.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Raise the request for refund or lodge.
6. Customer get the ticket number.

1. Open browser and enter URL. customer raise request for refund or
2. Login with valid credentials. complaint after 72 hours.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Raise the request for refund or lodge.

1. Open browser and enter URL. customer raise request for refund or
2. Login with valid credentials. complaint within 72 hours.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Raise the request for refund or lodge.
1. Open browser and enter URL. Customer manually handle the
2. Login with valid credentials. complaint.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Raise the request for refund or lodge.

1. Open browser and enter URL. Customer placed a BOPIS or ROPIS

2. Login with valid credentials. order.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer cancel the order.

1. Open browser and enter URL. Customer can cancel the order within
2. Login with valid credentials. 2 hours.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer cancel the order within 2 hours.

1. Open browser and enter URL. Customer can cancel the order after
2. Login with valid credentials. 2 hours.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer cancel the order after 2 hours.

1. Open browser and enter URL. Customer can cancel the order with 2
2. Login with valid credentials. hours.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer cancel the order after 2 hours.

1. Open browser and enter URL. Customer identifies an issue to the

2. Login with valid credentials. previous orders products.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer found the issues to the orders.
1. Open browser and enter URL. Customer raise the refund request,
2. Login with valid credentials. due to issue with order product.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer found the issues to the orders.
6. Customer raise a complaint to the order.

1. Open browser and enter URL. Customer identifies an issue to the

2. Login with valid credentials. previous orders products.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer cancel the order after 72 hours.

1. Open browser and enter URL. Customer could not raise the
2. Login with valid credentials. refund/complaint request after 72
3. Customer navigate to the my account. hour.
4. Customer select the previous order.
5. Customer cancel the order after 72 hours.

1. Open browser and enter URL. Customer could not raise the
2. Login with valid credentials. refund/complaint request within 72
3. Customer navigate to the my account. hour.
4. Customer select the previous order.
5. Customer cancel the order within 72 hours.

1. Open browser and enter URL. Customer can raise the

2. Login with valid credentials. refund/complaint request within 72
3. Customer navigate to the my account. hour.
4. Customer select the previous order.
5. Customer received the wrong item or
incomplete item.
6. Customer can raise a complaint or refund
within 72 hours.
1. Open browser and enter URL. Customer can raise the
2. Login with valid credentials. refund/complaint request after 72
3. Customer navigate to the my account. hour.
4. Customer select the previous order.
5. Customer received the wrong item or
incomplete item.
6. Customer can raise a complaint or refund
after 72 hours.

1. Open browser and enter URL. Customer can raise the

2. Login with valid credentials. refund/complaint request within 72
3. Customer navigate to the my account. hour.
4. Customer select the previous order.
5. Customer received the wrong item or
incomplete item.
6. Customer can raise a complaint or refund
within 72 hours.

1. Open browser and enter URL. Customer received not quality

2. Login with valid credentials. product.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer can raise a complaint or refund
within 30 days

1. Open browser and enter URL. Customer could not raise the quality
2. Login with valid credentials. complaint after 30 days.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer can raise a complaint or refund
after 30 days

1. Open browser and enter URL. Buyer purchased no-return policy

2. Login with valid credentials. products.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer can raise a complaint or refund
for non return products.
1. Open browser and enter URL. Buyer received wrong or damaged
2. Login with valid credentials. no-return policy products.
3. Customer navigate to the my account.
4. Customer select the previous order.
5. Customer received the wrong item or
damaged item.
6. Customer can raise a complaint or refund
for non return products.
 Medium Low
19 0

Test Device (for

Expected Results Test Data
mobile)

Verify that customer has placed an order NA Desktop

with home delivery, they decide to cancel
within 2 hours.

Verify that customer tries to attempt for NA Desktop

cancel the order after the 2-hour system
informs them that the cancellation period
has expired and they cannot cancel the
order without potential penalties.

Verify that customer tries to attempt for NA Desktop

cancel the order after the 2-hour system
informs them that the cancellation period
has expired and they cannot cancel the
order without potential penalties.
Verify that customer cancels the order NA Desktop
within the 2-hour window, he refund
process is initiated.

Verify that system fails to process the Desktop

refund due to a technical error,
and the customer is notified of the delay,
customer support is alerted to resolve the
issue.
NA

Verify that order has been marked as NA Desktop

delivered, customer discovers an issue
within 72 hours.

Verify that customer can raise a refund NA Desktop

request or lodge a complaint and receive a
ticket number and process initiation
notification.

Verify that customer tries to raise a NA Desktop

complaint or refund request after 72 hours.
System informs them that the
refund/complaint period has ended and
suggests contacting customer support for
further assistance.

Verify that customer raises a complaint NA Desktop

within the 72-hour window, system fails to
initiate the complaint process.
Verify that customer is notified of the issue NA Desktop
and customer support is alerted to
manually handle the complaint.

Verify that customer has placed a BOPIS or NA Desktop

ROPIS order, customer decide to cancel
within 2 hours.

Verify that customer can cancel the order NA Desktop

without any penalties and receive a full
refund of any advance payment made.

Verify that customer tries to attempt NA Desktop

cancel the order after the 2-hour window,
system informs them that the cancellation
period has expired and penalties as per
policy will apply.

Verify that customer can cancels within the NA Desktop

2-hour,if system encounters an error
processing the cancellation, customer is
notified of the issue and customer support
is alerted to assist.

Verify that customer identifies an issue to NA Desktop

previous order within the 72-hour period.
Verify that customer can initiate a refund NA Desktop
or complaint process and receive a ticket
number and notifications regarding the
process.

Verify that customer identifies an issue NA Desktop

after the 72-hour period, refund/complaint
period has expired.

Verify that system informs them that the NA Desktop

period has ended and directs them to
contact customer support for further
assistance.

Verify that customer try to initiates a NA Desktop

refund or complaint within 72 hour, system
fails to process it due to technical issues,
customer is notified and customer support
is alerted to handle the issue manually.

Verify that buyer has received the wrong or NA Desktop

incomplete item, buyer submits a return
request within 72 hours of delivery. System
should trigger the RMA(Return Merchandise
Authorization) process and notify the seller.
Verify that buyer tries to submit a return NA Desktop
request after 72 hours of delivery. System
should deny the request and notify the
buyer of the expired return window.

Verify that buyer has received a damaged NA Desktop

product, buyer submits a return request
within 72 hours of delivery. system should
trigger the RMA(Return Merchandise
Authorization) process and notify the seller.

Verify that buyer has received the item. NA Desktop

Buyer files a quality complaint within 30
days of delivery. System should trigger the
RMA process and involve the seller and
OEM (if necessary).

Verify that buyer tries to submit a quality NA Desktop

complaint after 30 days, system should
deny the complaint submission and notify
the buyer of the expired complaint window.

Verify that buyer has purchased a product NA Desktop

with a no-return policy. Buyer tries to
submit a return request. System should
deny the request and inform the buyer of
the no-return policy.
Verify that buyer has purchased a product NA Desktop
with a no-return policy. Buyer submits a
return request for valid reasons (wrong
item, damaged product, or quality
issues).system should allow the return
request and trigger the RMA(Return
Merchandise Authorization) process.
 Cycle 1
Total Not
Total Pass Total Fail Total Executed
Executed
0 0 0 0

Test Case Status

Bug ID Actual Results
Complexity Pass/Fail/NE

Medium

Medium

Medium
Medium

Medium

Medium

Medium

High

Medium
Medium

Medium

Medium

High

Medium

Medium
Medium

Medium

High

Medium

Medium
 High

Medium

Medium

High

High
High
 Cycle 2
% of test cases % of test cases Total Not
Total Pass Total Fail
executed failed Executed
0 #DIV/0! 0 0 0

Test Case
selected for test
cycle 1
Status
(Regression Remarks Bug ID Actual Results
Pass/Fail/NE
Testing/Newly
Added) or Not re-
tested?
Not yet written the
user stories.
 Cycle 2
% of test cases % of test cases
Total Executed Total Pass
executed failed
0 0 #DIV/0! 0

Test Case selected

for test cycle 2
(Regression Status
Actual Results Remarks
Testing/Newly Pass/Fail/NE
Added) or Not re-
tested?
 Cycle 3
Total Not % of test cases
Total Fail Total Executed
Executed executed
0 0 0 0

Test Case selected

for test cycle 3
(Regression
Bug ID Actual Results
Testing/Newly
Added) or Not re-
tested?
% of test cases failed
#DIV/0!

Remarks
 Conventions
1.Main functionalities are designed with font size of 11 and bold enabled and sub-functionalities (if any) are
designed with font size 10 and bold enabled.
2.Test case numbering format is followed as "<Project Name in 2 character length >- <Major functionality
name in 2 character length>-<Running numbers>". For example: In XX project, test cases for Admin
module are numbered as "XX-AM-001", "XX-AM-002" etc.

NOTE: For fields with sky blue background color data will be automatically calculated based on the formu

Template Usage Guide

To add test cases for a new module:
1. Make a copy of "(Module Name)" sheet.
2. Rename the sheet as the name of the new module.
3. In the summary sheet copy the row for "(Module Name)".
4. Write the name of the module in the first cell and hyperlink it to the corresponding sheet.
5. Verify the formulas and modify according to the previous row if required.
6. Remove the test/dummy rows from the test cycle summary from the summary sheet and also remove
the test/dummy sheets.
tionalities (if any) are
<Major functionality
ases for Admin

ed based on the formu

sheet.

et and also remove