Document of Understanding Catalyst IWC

Document of Understanding – Testing

Application Name: Catalyst IWC
Version: 2.0
Line of Service: Global TAS, Advisory, FSO
Portfolio: Advisory

TCS – EY Confidential
Document of Understanding Catalyst IWC

Notice
© 2018 Tata Consultancy Services Limited

The data contained herein shall not be disclosed, duplicated, or used in whole or in part for any
purpose other than to evaluate the proposal, provided that if a contract is awarded to this offer
as a result of, or in connection with, the submission of these data, the propose shall have the
right to duplicate, use or disclose the data to the extent provided in the agreement. This
restriction shall not limit the right to use information contained in the data if it is obtained from
another source without restriction.

All trademarks that appear in the document have been used for identification purposes only and
belong to their respective companies.

2
 Document of Understanding Catalyst IWC

Document Revision History

Version Date Author Change Description

0.1 26/08/2019 Saran Sathyan Initial version

1.0 27/08/2019 Saran Sathyan Final version

1.0 27/08/2019 Abey A Iype Mundackal Document Review

2.0 27/08/2019 Saran Sathyan Updates based on review comments

2.0 27/08/2019 Abey A Iype Mundackal Document Review

Point of Contacts

Role Contact Name Email ID Ph. No

Project Manager Jack R Forness Jack.Forness@ey.com +12018720217

Product Owner Mike DePriest Mike.DePriest@ey.com +12054587783

Dev Lead Aleida Villarreal Fajardo Aleida.Villarreal@cr.ey.com -

Test Architect Abey A Iype-Mundackal abey.iypemundackal@ey.com +14702681371

Escalation contact Kym Larche kym.larche@ey.com +14702681270

3
 Document of Understanding Catalyst IWC

About this Document

Purpose
This document is intended to:
 Capture the understanding of Catalyst IWC Application gained by the TCS team during QA Phase.
 This document shall not replace the existing Operating Manuals and Production Support Procedure
(PSP) documents but shall reference relevant sections of the documents.

Intended Audience
Document of Understanding would be the prime reference for testers who would need to understand the
functionality of the application for testing any enhancements.

Organization of this Document

Information in this document has been organized as follows:

Table 1: Organization of the Document

Chapter Description

Section 1 Overview

Section 2 Testing Scope

Section 3 Test Artefacts

Section 4 Test Data Configuration and Setup process

Section 5 Test Process & Defect Process

Section 6 Tools

Section 7 Templates

Section 8 Application Release info / Change Requirements / Upcoming Releases

Section 9 Test Environments and Details

Section 10 Metrics

Section 11 Key Stakeholders

Section 12 Project References if any

Section 13 Application Version History

4
Document of Understanding Catalyst IWC

Reference Documents
Table 2: Reference Documents

Access
Document Name Description
Path/Location

Requirement/Use Case
DevOps
documents User story details and other relevant requirement documents

This link directs to Test cases and Defects of Catalyst IWC application.
DevOps Artefacts DevOps

Architecture Document available in this path or please see this document

Catalyst Architecture SharePoint

5
 Document of Understanding Catalyst IWC

Contents
Overview: Catalyst IWC ............................................................................................................................... 7

Testing Scope ............................................................................................................................................ 8

1.1 In Scope................................................................................................................................................. 8
1.2 Out of Scope .......................................................................................................................................... 8
1.3 Test Phases and Testing Types Covered from Recent Releases.............................................................. 9

Test Artefacts ............................................................................................................................................. 9

1.4 Functional .............................................................................................................................................. 9
1.4.1 Mobile Interface/Mobile Testing Coverage ....................................................................................................... 10
1.4.2 Engaging Mobile Testing Team Process ............................................................................................................ 10
1.5 Automation ..........................................................................................................................................11
1.6 Database testing .................................................................................................................................12
1.7 Non- Functional ...................................................................................................................................12

Test Data Configuration and Setup Process ................................................................................................ 13

Test Process and Defect Process ................................................................................................................ 14

1.8 Testing Life Cycle Process ....................................................................................................................14
1.9 Defect Life Cycle Process .....................................................................................................................15

Tools ....................................................................................................................................................... 16

Challenges .............................................................................................................................................. 17

Templates ............................................................................................................................................... 18

Application Release Information/Change Requirements/Upcoming Releases ............................................... 19

Test Environments and Details ................................................................................................................... 20

1.10 New Environment Create Request Process ......................................................................................20
1.11 Existing Environment Details Used for Application ..........................................................................20

Metrics.................................................................................................................................................... 21

Key Stakeholders ..................................................................................................................................... 22

Project References (if any)......................................................................................................................... 23

Application Version History ....................................................................................................................... 24

6
Document of Understanding Catalyst IWC

List of Figures
No table of figures entries found.

List of Tables
Table 1: Organization of the Document .............................................................................................................................. 4

TCS – EY Confidential
Document of Understanding Catalyst IWC

List of Abbreviations
Table 3: List of Abbreviations

Abbreviation Expanded Form

ALM Application Lifecycle Management

DSR Daily Status Report
KPI Key Performance Indicators
KT Knowledge Transition
NA Not Applicable
NFR Non- Functional Requirement
TA Test Architect
TCS Tata Consultancy Services
TFS Team Foundation Server
UAT User Acceptance Testing
WSR Weekly Status Report

vii
Document of Understanding Catalyst IWC

Overview: Catalyst IWC

Catalyst: IWS is a program which combined with Catalyst IWC and MEMS.

This is a shop floor execution application which helps the daily tasks of the workers in the production plants. This
application visualizes the deep production line performance, disparate systems and normalizes data. It also automates
the workflows to support Shift Handover, Line DDS and roll up into Department and Plant Level Daily and Weekly Direction
setting.

Below are the modules in the Catalyst: IWS application:

 Safety Incident elimination

 Quality Incident elimination
 Breakdown elimination
 Maintenance planning & scheduling
 Changeover efficiency

1.1 Business Overview

Catalyst IWS “Integrated work systems” release focuses to automate 5-additional shop-floor functions and enhance
original Smart Factory release. In addition to automating 5-additional functionalities, the objective is also to move
into CTP “Client Technology Platform” environment to enable quicker delivery and stand-up for new clients.

1.2 Functional Overview

Catalyst IWC application has Five main modules and 3 user Roles.

Please refer to the attached document for the detailed Functional Overview.

Catalyst IWC.pptx

TCS – EY Confidential 7
Document of Understanding Catalyst IWC

Testing Scope

1.1 In Scope

Static testing, Smoke testing, System/Functional testing, System Integration testing, Data Validation testing,
Automation testing, Mobile Testing and Regression testing are in scope for Catalyst IWC application.

1.2 Out of Scope

 Security Testing is performed by the InfoSec team

 Performance Testing – Currently Not in scope

 UAT/Production Verification testing is performed by Business team

TCS – EY Confidential 8
Document of Understanding Catalyst IWC

1.3 Test Phases and Testing Types Covered from Recent Releases
Table 5: Test Phases and Testing Types Covered from Recent Releases
Test Phase Test Types Existing Test Responsible Team Environment
Scope (Y/N)
Initiation and QA team validated the
Planning - requirement
Y QA Environment
requirements and document/user stories
document review Static Testing

Unit Testing / Infrastructure Readiness

Component Testing Testing
Y
Phase
Unit Testing Dev team Dev Environment

Installation Testing

System Testing / System / Functional Y

System Integration Testing
Testing Phase
System Integration Y
Testing QA Environment

Data Validation Testing Y QA team

Smoke Testing Y

Regression Testing Y

User Acceptance End to End Testing / User Y UAT team / Business

Testing Acceptance Testing

Non- Functional Performance Testing* N* Not Applicable* TBD*

Testing

Security Testing/ Y InfoSec team QA Environment

Information Security
Certification Testing

Desktop Impact & Testing N Not Applicable

Digital Testing Mobile Testing* Y Mobile Testing Team QA Environment

TCS – EY Confidential 9
Document of Understanding Catalyst IWC

Test Phase Test Types Existing Test Responsible Team Environment

Scope (Y/N)
Operations Acceptance N
Testing

Operational Testing N Not Applicable Not Applicable

Backup / Restore Testing

HA / DR Testing N

Monitoring Testing N

Prod Verification Test Production Verification N Not Applicable Not Applicable

Testing

Performance Test – As of today (27 August 2019) Performance test is still not in scope for QA.

Once it become scope it will be execute on QA environment.

TCS – EY Confidential 10
Document of Understanding Catalyst IWC

Test Artefacts
Table 6: Test Artefacts

Artefact Location

Test Strategy Document SharePoint

Use case documents
DevOps User Story Section

DevOps Test Module

Test Plan

DevOps Test Module

Test Cases

DevOps Repro
Automation Scripts

DevOps Test Module

Test Execution Results

SharePoint
Test Completion Report

1.4 Functional

 The end-to-end QA functionality of the project is managed through DevOps.

 This project follows Agile methodology and all the test cases and defects are documented in DevOps.

 Product Owner created all user story on DevOps

 QA refers to the user story and create test scenarios and test cases. QA test and verify whether the main components
are functioning in accordance with the business requirements provided for release.

 Catalyst IWC environment can be accessed from the below URL.

Catalyst IWC

TCS – EY Confidential 9
Document of Understanding Catalyst IWC

1.4.1 Mobile Interface/Mobile Testing Coverage

 Mobile Testing done on IOS and Android devices

 During second phase of mobile testing, Project Manger informed to test only on iPad Pro

 Mobile Testcases were tracked on DevOps – Test plan

Device Resolution OS Version Browser

iPad Air 2 2048*1536 iOS 11.4 Chrome

iPad Pro 2048*2732 iOS 11.2.1 Chrome

Samsung Galaxy S2 Tab 2048*1536 Android 7.0 Chrome

1.4.2 Engaging Mobile Testing Team - Process

 Mobile Testing is performing at end of each phase once the desktop is Stable.

 Separate GTS Ticket were raised for mobile testing

 Desktop team will review the entire requirement for the sprints which are in scope for each phase and Identify
the scope for Desktop and Mobile Testing. This scope items for mobile scope will be shared with PM and PM
will raise a GTS ticket to engage mobile testing team only for those items in scope

 Desktop QA Team will provide functional Knowledge transfer to mobile team, so they can start easily.
Reporting for Mobile testing is along with Desktop in Daily stand-up call and in weekly status report

 Mobile Defects ,Scripts are handled on DevOps

TCS – EY Confidential 10
Document of Understanding Catalyst IWC

1.5 Automation

We have achieved 88 % functional automation for Catalyst IWC.

Automation script is maintained in the given path - Automation Commented [SS1]:

Commented [SS2]: More details for Automation
regression
achivement
cycles and save

TCS – EY Confidential 11
Document of Understanding Catalyst IWC

1.6 Database testing

Data base Testing: QA validate records for all modules in Database and User roles are changed from Database.

Db Scenarios.xlsx

1.7 Non- Functional

 Security testing is performed by InfoSec team

TCS – EY Confidential 12
Document of Understanding Catalyst IWC

Test Data Configuration and Setup Process

The test data can be controlled from the application. The admin user can manipulate the contents in the frontend and add
any details based upon the test cases form the admin section.
Test Data:

Catalyst_Test_Data.
Db Scenarios.xlsx
docx

 We have a dependency for testing Production / Maintenance module. SAP feed data also reflected on this module, so
development team agreed that they will provide SAP data to QA team for verification
 This is still pending with development team as of August 27, 2019

 This application has a dependency with the assets which mapped to time zone. So, if the asset is mapped to US time
zone then on MY Task and defect modules the records will display only if we change QA machine time zone to
International time zone. So, once we did this then all the Task related to the selected asset will be listed on listing table.
 All asset under is mapped to IST time zone, so QA team can use this asset to test it within IST time zone. (AKY INC > AKY
Beverage Inc > AKY Beer Co)

TCS – EY Confidential 13
Document of Understanding Catalyst IWC

Test Process and Defect Process

1.8 Testing Life Cycle Process

Reporting will be only WSR and the Daily stand up.

Summary of Test Execution and defect count (new/fixed/closed/re-opened) to be shared by QA in daily Stand-up

The WSR document will contain the following sections:

 Executive Summary

 Key Accomplishment this Period

 Activities behind Schedules

 Key Activity planned for next week

 Milestone

 Matters of Immediate Attention

 General Comments

 Key Risk /Issues

Once test execution is completed and code is ready for implementation, a final Test Closure Report will be issued by the Test
Lead/Manager.

TCS – EY Confidential 14
Document of Understanding Catalyst IWC

1.9 Defect Life Cycle Process

To ensure that defects found are managed in an efficient and repeatable manner with good visibility to all stakeholders, a
defect lifecycle must be defined. This defect lifecycle tracks the life of the defect from the moment it is first encounter through
analysis, resolution, re-testing and closure.

For this project, this process will be followed from the System/functional testing phase.

Scrum team need to triage defects that disagree between Dev & QA. All new defects will be triaged by the QA & Dev of the
respective story.

Test scenarios, test cases and defects are uploaded to DevOp for future reference/reuse and execution of the test cases would
be performed in DevOps

TCS – EY Confidential 15
Document of Understanding Catalyst IWC

Tools

The following tools are used in the overall test and defect management process in Catalyst IWC

 Test Management/Defect Management tool – DEVOPS

 Automation Tool – Visual Studio with Selenium C#

 Google Chrome with Latest Version

 Microsoft SQL Server 2014 Management Studio

 SeeTest Mobile Automation Tool

TCS – EY Confidential 16
Document of Understanding Catalyst IWC

Commented [SS3]: Dependency with Mike

Challenges Dependency with timezone
Retro on IST timezone

TCS – EY Confidential 17
Document of Understanding Catalyst IWC

Templates
Table 8: Templates details

Template Name Template description Document/Access Path

This link directs to templates used for Test Plan, Test

case and Test Completion report can be accessed Template Reference Link
Test Artefacts template from the given link. These are the standard templates
used for creation of Test Plan, Test case and test
completion report for Catalyst IWC application.

This link directs to template used for test scenarios Test Scenarios
Test Scenario template
preparation.

Templates used for Weekly Status reporting are

WSR template* Catalyst
attached
IWS_Testing WSR_02_Aug_2019.pptx

 WSR - This projects WSR type is External and this will be shared with project team.

 WSR needs to be reviewed with Test Architect on Thursday evening IST time zone and this will be send to PM on
Friday evening IST.

TCS – EY Confidential 18
Document of Understanding Catalyst IWC

Application Release Information/Change

Requirements/Upcoming Releases
The table briefly explains the previous releases of the application.
Table 9: Catalyst IWC Release details

SL. No App Name and Versions # Description Version revised date

1 Catalyst IWC, Release 1 Phase One TBD

TCS – EY Confidential 19
Document of Understanding Catalyst IWC

Test Environments and Details

1.10 New Environment Create Request Process

Test Architect identifies the environment needed for testing and the request is raised to development team to deploy the
developed application into QA environment.
The PM of the project and Development team are responsible for creating QA environments as prerequisites to start QA
process during the first release. Then QA Lead share this detail with QA team once the environment is ready.

1.11 Existing Environment Details Used for Application

The following table gives the existing environment details of Catalyst IWC application. These links are accessible under
specified domain only.

Table 10: Existing Environment Details Used for Application

Test Phase Environment Environment/Deployment Owner

Unit Test Dev Dev Local Machine

System Test & Site https://apps-

System Integration QA dev.ci52gnnwyz.catalyst.ey.com/dashboard?id=82&ln=en-
Test (ST&SIT) usURL

User Acceptance
UAT TBD
Test (UAT)

TCS – EY Confidential 20
Document of Understanding Catalyst IWC

Metrics
Test Execution Summary metrix : Please see section 5.2

Defect Summary metrics: Status as of 26 August 2019

Fig 5: Defect Summary

TCS – EY Confidential 21
 Document of Understanding Catalyst IWC

Key Stakeholders
Point of contacts and another key stakeholder’s information are as listed here:
Table 11: Key Stakeholders

Role Contact Name Email ID Ph. No

Project Manager Jack R Forness Jack.Forness@ey.com +12018720217

Product Owner Mike DePriest Mike.DePriest@ey.com +12054587783

Dev Lead Aleida Villarreal Fajardo Aleida.Villarreal@cr.ey.com -

Test Architect Abey A Iype-Mundackal abey.iypemundackal@ey.com +14702681371

Test Lead Saran Sathyan Saran.sathyan@ey.com +91 8281768700

Mobile Test Lead Sunla S Purakkeli Sunla.S.Purakkeli@ey.com -

Catalyst Support Team applications@catalyst.ey.com

TCS – EY Confidential 22
Document of Understanding Catalyst IWC

Project References (if any)

Please refer to the following table for the project related documents:

Table 12: Reference Documents

Access
Document Name Description
Path/Location

Requirement/Use Case
DevOps
documents User Story details

This link directs to Test cases and Defects for Catalyst IWC application.
DevOps Artefacts DevOps

Architecture and other This link directs to SharePoint

SharePoint
documents

TCS – EY Confidential 23
Document of Understanding Catalyst IWC

Application Version History

Please refer to the above section (Section 8) for Application version history.

TCS – EY Confidential 24