1.

Purpose
The purpose of this document to give the high level view of the automation test
approach, scope and risk based testing required for Jupiter program.

2. Building blocks of automation approach

Test Automation Framework
Tools Required
Scope
Phases
Resource Mapping
Timeline/Roadmap

2.1 Test Automation Framework

The Framework outlined here is based on the use of UFT as functional automation
tool and ALM as test management tool. This framework is a hybrid framework.
Below is the architecture of the framework, in the diagram the bidirectional arrows
from the Test Case Script to the Test Resources and Test Plan indicates control
flow from the test case script to the assets. After processing, the control returns
back to the test case script.

Diagram: Framework Architecture

2.1.1. Components of Framework
Driver Script
Test Scripts
Function Libraries
o Common function library for all
applications
o Specific function library of each
application
Shared object repositories
External Data sheets
Reporting
Recovery Scenarios
Environment Setting files

2.1.2. Assumptions

It is being assumed that a new framework from scratch is to be created, following

the guidelines provided in the Framework Design document from BMO.

2.2. Tools Required

UFT will be used for the functional automation of all the application in scope, taking
in assumption that the required add-ins are available to be used with UFT for the
applications in scope. ALM will be used as test management tool and UFT scripts will
be managed in ALM in a defined directory structure as per the guidelines in
Framework design document. and will be triggered from ALM only.

2.3. Scope

All the applications have been majorly distributed under 5 tracks mentioned below:
Automation Services & Content Mgmt.
Customer Service and Asset Management
Sales and Originations
Service Delivery and Ops Excellence
Sub-Ledger & Portfolio Management

.
Types of applications based on their technical architecture have been broadly
categorized as below:

Web Applications
Mainframe Applications
Database applications
Web services
Batch Processes
Feasibility of automation on all the above 5 types of applications have yet to be
confirmed. Out of total manual test cases, approximately 30% test cases will be
covered as part of automation regression suite. Which will be automated in a 3
phased approach.

2.4. Phases
Automation Regression suite will be created from the manual test cases which
would have been segregated as good target for automation as well as they are
feasible for automation.
Overall automation will be divided into 3 phases:

2.4.1. Planning and Feasibility Analysis : Phase 1

In this phase below mentioned activities will be conducted. This is very crucial
phase as, activities conducted in this phase will act as the base of overall
automation.

Knowledge Transfer : Functional as well as technical/architectural

knowledge of each and every application will be conducted.
POC : POC on all the applications in scope will be conducted , to
confirm their feasibility.
Framework Development (Once the applications are available
in Test environment) : A base framework skeleton will be created and as soon
as the applications are available in automation environment , below mentioned
tasks for framework designing will be done.

Utility Functions Library

Creation
Shared Object Repositories
Creation
Basic Recovery Scenarios
Creation
Test Settings and Add-on set up
for all applications
 Scripts segregation : First the scripts will be segregated from the
manual test cases based on below criteria :

Test cases to be verified with

different set of data.
Test cases has complex
business logic/Calculations, which may lead to manual error.
Test cases to be verified on
multiple browsers
Test cases to be verified on
multiple platforms
Test cases to be verified with
multiple user types
Then the targeted/segregated Automation scripts will be further segregated based
on below criteria :
Automation Feasibility
Priority ( Based on applications
priority P1/P2/P3/P4)
Complexity (High/Medium/Low)
as per the number of steps involved, number of
validations(business/database/arithmetic) ,complexity of the flow
,knowledge of the functionality etc.
ALM structure : Directory structure in ALM will be
created for automation test scripts ,as advice in framework design document.

2.4.2. Test Script Designing : Phase 2

This is the Test scripts creation phase. Which is further divided into two phases
Phase 2a and Phase 2b.

2.4.2.1. Phase 2a

This is the Test scripts creation phase one .

In this phase 50%-60% of the test scripts under the scope
of automation will be created.
The script creation activity will be divided as per
respective tracks and their teams.
Test scripts for the applications with priority P1 and P2 will
be done first.
Team velocity/Test Script creation productivity / person
will be taken as the base for daily targets and reporting.

2.4.2.2. Phase 2b
This is the Test scripts creation phase two. In this phase rest of the scripts in scope
i.e. remaining 40%-50% will be targeted mainly with priority P3 and P4. Rest of the
activity will remain same as phase 2a.

2.4.3. Test Script Execution : Phase 3

This is test script execution phase. Which is further divide in two phases Phase 3a
and Phase 3b.

2.4.3.1.Phase 3a

This is the Test scripts execution phase one. This is End to End testing phase, along
with manual testing in this phase automation scripts created for regression suit in
Phase 2a with priority P1 and P2 will be executed.

2.4.3.2.Phase 3b

This is the Test scripts execution phase two. In this phase automation scripts
created for regression suit in Phase 2b will be executed. This is a post go live phase,
so the scripts left in phase 3a and with priority P3 and P4 will be executed.

2.5. Resource Mapping

It is being assumed that automation team will be divided among 3 tracks.Which will
further be aligned with the 5 functional tracks of the jupiter program.Each track will
consists of 1 Technical lead and 4/5 automation resources. All the 3 tracks will be
headed by a Automation Test manager.

2.6.Automation Road Map

2.7.Risks/Assumption

S.NO Risk Description Assumptions

1 On time
Availability/Onboarding
of automation resources
2 On time availability of
Automation Test
environment.
3 Virtual Machine network
stability/availability.
4 Test Data availability for
automation testing.
5 Test User's availability to
test/cover all the end to
end scenarios.
6 On Time Framework
setup and detailed
feasibility analysis of all
the application in scope.