TMP 037 : Test Case

Test Report (ID: EBO_TC's, Version 1.0.0, Classification: Confidential)

India
Document Identification
Title: EBO_Test Case
Subject: Test Cases
Version: 1.0
Issue Date: 6/Sep/2021
Author: Yogesh C

Revision History
Date Sheet name Version Description Revised By Reviewed By Approved By Approved Date
6/Sep/2021 EBO_BAP_428 1.0 EBO Promise block - Returns icon Chandna A R

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

TMP 037 : Test Case

Test Cycle No. 1

Test Case Complexity
Total No. Not Not A
Module Pass Fail Test Date
of T.C's High Medium Low Executed Bug
EBO_1 4 3 1 0 0 0 0
Total 4 3 1 0 0 0 0

Test Cycle No. 2

Test Case Complexity
Total No. Not Not A
Module Pass Fail Test Date
of T.C's High Medium Low Executed Bug
EBO_1 0 0 0 0 0 0 0
Total 0 0 0 0 0 0 0

EBO_1
Test Case Complexity
Total No. Not Not A
Module Pass Fail Test Date
of T.C's High Medium Low Executed Bug
EBO_1 0 0 0 0 0 0 0
Total 0 0 0 0 0 0 0

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

 TMP 037 : Test Case

Test Cycle No. 1

Defects/ No.Test
Total Effort Total Approval Justification/
No.Test cases cases /Effort
(man hours) defects for release Remarks
[Actual] [Actual]

Test Cycle No. 2

Defects/ No.Test
Total Effort Total Approval Justification/
No.Test cases cases /Effort
(man hours) defects for release Remarks
[Actual] [Actual]

EBO_1
Defects/ No.Test
Total Effort Total Approval Justification/
No.Test cases cases /Effort
(man hours) defects for release Remarks
[Actual] [Actual]

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

TMP 037 : Test Case

Total No. Of Test Cases : 4

High Medium
Complexity Count :

3 1
Test Cases Executed By :
Test Environment :

Test Case Test Case Pre Condition

Test Case Description Test Step Expected Results
# Type (If any)

Functional/P User has

TC_001
ositive Steps: access to PDP
Verify for text in Return window when product is 1. Tap on app icon in mobile and Launch app User should be able to view Return text as per Admin
returnable 2.Navigate to PDP configuration(Example : 7 Days Returnable)

User has
TC_002 UI Steps:
access to PDP
1. Tap on app icon in mobile and Launch app
Verify Return window UI 2.Navigate to PDP Return window UI should be displayed to user as per UI/UX

Functional/ Steps: User has

TC_003
Negative Verify for text in Return window when product is not 1. Tap on app icon in mobile and Launch app access to PDP
returnable 2.Navigate to PDP User shouldn't be able to view Return text in this case

Functional/P User has

TC_004 User should be able to see message as 'Non Returnable' in this case
ositive access to PDP
Steps:
Verify for text in Return window when product is non 1. Tap on app icon in mobile and Launch app
returnable 2.Navigate to PDP

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

TMP 037 : Test Case

Cycle 1 Cycle 2 Cycle 3

% of test % of test % of test % of test

Total Not Total Total Not Total Total Not Total
Low Total Pass Total Fail cases cases Total Pass Total Fail cases cases Total Pass Total Fail
Executed Executed Executed Executed Executed Executed
executed failed executed failed
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Test Case Status Status Status

Complexit Pass/Fail/ Defect ID Actual Results Remarks Pass/Fail/ Defect ID Actual Results Remarks Pass/Fail/ Defect ID Actual Results
y NE NE NE

Not
High
Executed

Not
Medium
Executed

Not
High
Executed

Not
High
Executed

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

TMP 037 : Test Case

Cycle 3

% of test % of test
cases cases
executed failed
0 0

Remarks

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

 Acceptance Criteria
Acceptance Criteria -
If the Product is not returnable then show as “Non Returnable”.
If the product is returnable then show the return window in text for example “ 7 Days Returnable” accordingly

Page 7
 Acceptance Criteria
Test cases

Page 8
 Test Case Complexity Guideline
· Multiple tasks performed.
· Doing complex calculations.
High
· Accessing the data from multiple tables from the database.
· Updating data to multiple tables in the database.
· Accessing the database.
Medium · Selecting data from a table and displaying in the UI.
· Performing validations.
· Simple entry in the UI.
· Display of simple popup windows without any data population.
Low
· GUI enable and disable.
· No validation checks performed.

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 SunJewels project, test cases for
Admin module are numbered as "SJ-AM-001", "SJ-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
ct, test cases for

ed based on the formu

sheet.

eet and also remove