0% found this document useful (0 votes)
37 views8 pages

TCs MAG 273 Test Case

The document is a test report for the EBO_Test Case, detailing the execution of 13 test cases with a complexity breakdown of 6 high and 7 medium. It outlines acceptance criteria for SKU cancellation, including mandatory details and validation checks. Additionally, it provides guidelines for test case complexity and conventions for numbering and formatting test cases.

Uploaded by

bala govindam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
37 views8 pages

TCs MAG 273 Test Case

The document is a test report for the EBO_Test Case, detailing the execution of 13 test cases with a complexity breakdown of 6 high and 7 medium. It outlines acceptance criteria for SKU cancellation, including mandatory details and validation checks. Additionally, it provides guidelines for test case complexity and conventions for numbering and formatting test cases.

Uploaded by

bala govindam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd

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: 23/Sep/2021
Author: Sreekanth Chintha

Revision History
Date Sheet name Version Description Revised By Reviewed By Approved By Approved Date
23/Sep/2021 EBO_MAG_273 1.0 Cancellation - Selection of SKU for creating the cancel request

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 13 6 7 0 0 0 0
Total 13 6 7 0 0 0 0

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


TMP 037 : Test Case

Total No. Of Test Cases : 13

High Medium Low


Complexity Count :

6 7 0
Test Cases Executed By :
Test Environment :

Test Case
Test Case Test Case Pre Condition
Test Case Description Test Step Expected Results Complexit
# Type (If any)
y

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

Cycle 1

% of test
Total Not Total
Total Pass Total Fail cases
Executed Executed
executed
0 0 0 0 0

Status
Pass/Fail/ Defect ID Actual Results Remarks
NE

TMP 037 : Test Case Version No 3.0 Release Date: September 8, 2010CONFIDENTIAL 4
Acceptance Criteria
Acceptance Criteria -
When one SKU is selected for cancellation, the app will navigate to another page which will have the list of all the SKUs in
will have the following details:
1. SKU Title
2. Picture of SKU
3. Order price
4. Quantity available for cancellation.
The item through which cancellation is triggered in the order detail page will be auto ticked and show the details as below.
The SKU that has been ticked will show the following details. All the details are mandatory to be filled to accept the cance
1. SKU Title
2. Picture of SKU
3. Order Price
4. Quantity available for cancellation
5. Reason for cancellation
6.Quantity to cancel (This can be +/- change or direct value entry.)
The quantity to be returned will have the following checks:
1. The quantity cannot be more that the Quantity available for cancellation.
2. If selected, it cannot be 0.
The options to be shown for Reason for Return are as below:
1. Wrong Item Shipped (includes wrong customization) 
2. Change in mind 
3. Excess quantity ordered 
4. Others (30 char - free text)
Cancellation policy to be given as a link below for customer to open. It should take the customer to a separate page where
There needs to be a stick footer which will show the following:
1. Total SKUs selected for cancellation
2. Button for request processing with message “Proceed to confirm cancellation”
The “Proceed to confirm cancellation” will be highlighted if there is atleast one SKU selected with atleast one quantity.

Page 5
Acceptance Criteria
Test cases

Page 6
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)

<Major functionality
ct, test cases for

ed based on the formu

sheet.

eet and also remove

You might also like