Test Case v1.0 (Kroger)
Test Case v1.0 (Kroger)
A
Overview of Test Execution Monitoring Report Test case template would be used for preparation of test cases for projects.
This Test Case template is released for use in Tata Consultancy Services Limited (TCS) with effect from 14/Ap This document is subject to TCS Document Control Procedure. Softcopy of the latest version of the document is available in Document Repository. Comments, suggestions or queries should be addressed to Assurance Services Unit Head.
Approved By:
Date: 14/Apr/20
Authorised By: Assurance Services Unit Head Revision Details: Version No./Revision No. 1.00
Date: 14/Apr/2
TCS SENSITIVE
Page 1
Read Me
Test Case
Apr 2009
ository.
es Unit Head.
Date: 14/Apr/2009
Date: 14/Apr/2009
TCS SENSITIVE
Page 2
<Project Name> Test Case Name: <Test Case ID>_<Test Case brief description>
Project / Change Request ID #: Release Details: Type of Testing : <System Testing / Integration testing / UAT etc> Test Case ID : <ID> Test Case Description : Test Case Priority : Test Objective : Based on HLD/LLD Version #: <Version Details> Requirement/Use Case ID : <ID> Test Case Version #: <Version Details> Automation Reference : Mention reference to any automation script developed for this test case here Project Team Name:
Test Specs prepared by: Test Specs reviewed by: Unit/module tested by: Verified that all comments are closed/Verified by: <Name> Prepared date: Review date: Tested date: Verified date: MM/DD/YYYY MM/DD/YYYY MM/DD/YYYY MM/DD/YYYY Review passed: Test passed: Estimated Time to Complete
Pre-Condition
e.g. User has access to System environment etc
Revision History
Revision Description Change type (add/Modify/delet e)
Version #
Date
Test Steps
Test Case #
Test Step # OMNI81_TC_M2.10 OMNI81_TC_M2.11 OMNI81_TC_M2.12 OMNI81_TC_M2.13 OMNI74_TC_M2.20 OMNI74_TC_M2.21 OMNI74_TC_M2.22 OMNI74_TC_M2.23 OMNI74_TC_M2.24 OMNI74_TC_M2.25 OMNI74_TC_M2.26
Expected Result
Real-time synchronization of two shoppers' web Synchronization stablished browsers to create a single collaborative shopping session Agent navigate customer browse take control of the session agent can navigate the customer Agent highlight the web page elements Customer can see those visual cues Agent submit the order Order placed Open the OMNI-18 session existing order submitted to the store with new quantity. Try to increase existing order Quantity Edit the order and save changes Try to reduce existing order Quantity Cancel the order Cancel the order
Open the OMNI-18 session Select view and manage the existing orders. Select an order Select total orders waiting to be fulfilled Select view and manage the existing orders
System should display the OMNI- Agent can place the orders(OMINI18 session. 18) Quantity cannot be increased on the existing order. new order placed for additional quantities Item status will change to "modified" new order placed for new quantities. can not cancel.(Order routing to the store) Item status will change to "Cancel"(Order no routing to the store) System should display the OMNI- Orders is already placed 18 session. The order queues must be displayed. Further details about that order displayed. Display a full order summary The order queue should display high level details( Type of order - Order Identifier - Status of the order -- order placed -- order sent to store -- order acknowledged by store - Time of order -- TBD) Logined as Support Agent Identified as TBD Order submited conformation Submited by Support agent and him information
OMNI19_TC_M2.34
Open the OMNI-18 session Identify Support agent as TBD submit the order on behave of customer Order submition status
Business Priority
LLD#
Additional Comment
Status
Iteration # NN Planned Actual Defect ID (if Actual result Data Date Date Failed)
Comments / Attachments