Test Automation Framework Design

For
BNYM ADR Application

Name Business Group / Vertical

Author Wipro Technologies, Bangalore BFSI - Securities
Reviewed By
 Test Automation Framework BNYM - WIPRO

Revision History

Version Date of Description of Reason for Affected Sections Approved

(x.yy) Revision Change Change By
1.0 09/26/2008 Initial Version Gangadharan

Wipro Technologies Confidential Page 2 of 35

 Test Automation Framework BNYM - WIPRO

Table of Contents:

1 Introduction................................................................................3
1.1 PURPOSE.............................................................................................3
1.2 SCOPE:................................................................................................3
1.3 OUT OF SCOPE:....................................................................................3
1.4 TARGET AUDIENCE:..............................................................................3
1.5 ACRONYMS AND DEFINITIONS:..............................................................3

2 BNYM Test Automation Framework:...........................................3

2.1 TEST AUTOMATION FRAMEWORK DESIGN:...............................................3
2.2 TEST AUTOMATION FRAMEWORK COMPONENTS:......................................3
2.2.1 Generic/Common Libraries:...................................................................3
2.2.2 Application specific Function Library......................................................3
2.2.3 Test Data Files:......................................................................................3
2.2.4 Functional/Modular Scripts:...................................................................3
2.2.5 Driver Scripts:........................................................................................3
2.2.6 Object Repository:.................................................................................3
2.2.7 Result Files:...........................................................................................3
2.2.8 Project Directory Structure:...................................................................3
2.3 ERROR HANDLING AND RECOVERY:........................................................3
2.4 CODING STANDARDS:...........................................................................3

3 Automation Execution Flow:.......................................................3

4 Re-usability:...............................................................................3
4.1 COMMON UTILITY FUNCTION LIBRARY:...................................................3
4.2 APPLICATION SPECIFIC FUNCTION LIBRARY:...........................................3
4.3 REUSABILITY OF TEST DATA:.................................................................3

5 Extensibility:...............................................................................3
6 Configuration Management............................................................3

Wipro Technologies Confidential Page 3 of 35

 Test Automation Framework BNYM - WIPRO

Confidential information:

This document contains confidential information. The contents of this document may not
be transmitted or reproduced for use or distribution without express permission of Bank
of New York Mellon and WIPRO Ltd.

Wipro Technologies Confidential Page 4 of 35

 Test Automation Framework BNYM - WIPRO

1 Introduction

This document is aimed to provide a design for developing test automation suite for
testing BNYM – ADR Applications (Both Master File (MF) and Corporate Actions (CA))
using Quick Test Professional v9.5 (QTP).

1.1 Purpose

The purpose of this document is to address the test automation framework for BNYM
– ADR Applications Regression Test Suite. The coverage includes automation
framework design, folder structure, reusability plan and coding guidelines.

1.2 Scope:

Scope of Automation Service

 KAP phase depicting the Knowledge Acquisition.

 BNYM needs to provide a detailed understanding of the test cases, provide
installation assistance in the beginning. Also BNYM needs to provide a
technical assistance when there are clarifications needed or during work-
around baselines.
 Design & implement of an automation framework.
 Automated Scripts using QTP 9.5 for the identified set of functional test cases
only from the Regression Test Suite.
 Script Hand-holding document shall be delivered during the end of
automation.
 Updates to the scripts based on the updates to the application / test cases,
whenever the changed test case or application is proposed by BNYM to be
used for further automation, any time during the engagement. This is
subjective to the change management process.

This document focuses on the Automation Framework that shall comprise of:
 Function library where generic and application specific reusable functions are
created and maintained

Wipro Technologies Confidential Page 5 of 35

 Test Automation Framework BNYM - WIPRO

 Test Data Sheets where test data are created and maintained. This will
contain data that needs to be entered in to application and expected results if
any.
 Shared object repository where object properties and values are created and
maintained.
 Script repository where automated test scripts are created, organized and
maintained specific to the Application functionality
 Reusability, Maintainability and Extensibility with Resiliency

It will not discuss the specific architectural decisions and mechanisms i.e. the
detailed architectural specifications required for the actual implementation. Specific
architectural decisions here are at very granular level i.e. at the script level, the
related script interactions, specific libraries, their implementations and their usage.
In nut shell, the framework deliverable doesn’t focus on detailing the artifacts at the
test case and script level. The focus here is, depicting the place-holders for test-data,
function-libraries, modularity with significant exemplification using couple of
examples only. It also depicts the extensibility and resiliency considerations of the
framework. The detailed artifacts are nothing but the test scripts by themselves
which are deliverables of the Construction phase and have a separate acceptance
criteria for the same. Framework is a strategy deliverable out of the Elaboration
Phase.

1.3 Out of Scope:

Wipro Services Out of Scope

 Automation of test cases other than regression test cases.
 Testing of Backend applications/ Databases.
 Application Intrusive testing.

Automation Services Out of Scope

 Training of the BNYM personnel for the usage of Automation tool or on
the recorded scripts
 Any third party interfaces / external interfaces
 Database Verifications

Wipro Technologies Confidential Page 6 of 35

 Test Automation Framework BNYM - WIPRO

 Automation of test cases which relate to Software Installation and

verification

1.4 Target Audience:

The following are the target audience for this document

 BNYM Product Managers, Program Managers and Test Analyst
 Wipro - BNYM Test Automation team

1.5 Acronyms and Definitions:

The following are the acronyms and their definitions used in the document:

Term Definition
BNYM Bank of New York Mellon
ADR American Depository Receipts
QTP Quick Test Professional
AUT Application Under Test
MF Master File
CA Corporate Actions
M/C Machine (Desktop)

Wipro Technologies Confidential Page 7 of 35

 Test Automation Framework BNYM - WIPRO

2 BNYM Test Automation Framework:

Specific to modularity & functional decomposition strategies available in the ADR

application and the test case design specifications that include the test steps, pre-
conditions (translates into re-usable functions) test data association with the test
steps, hybrid framework has been identified as the framework solution proposition.

The following constitutes for the hybrid framework proposition for ADR application.
 Functional De-composition: Each of the ADR applications is broken in
to different functions to form a library (e.g. Search, Filter, Upload, etc.)
 Data driven approach: This approach is used to input the value into
the ADR Application (UserID, Password, search criteria, search result headers,
etc) using data sheet.
 Keyword driven approach: Sometimes it may be required to
parameterize the Browser, page and controls (Push button, combo box, check
box) logical names or physical descriptions (mapped with QTP’s object repository)
along with the operations on controls (Click, select, Search, Clear). Such
parameterized values may be maintained in excel data sheet.

2.1 Test Automation Framework Design:

High level Automation Framework diagram is depicted below.

Wipro Technologies Confidential Page 8 of 35

 Test Automation Framework BNYM - WIPRO

The benefit of this approach is the ability to re-use functions across ADR application
modules. In addition, the functions can be easily maintained in case of any functional
enhancements / modifications to future releases of Enterprise Suite and allows
leveraging the modules / scripts into future releases. An intuitive and efficient test
management strategy to organize scripts, Libraries, Object repository and Data files
is adopted which aims to create a framework and lay the foundation of the testing
workflow.

The components of test automation framework are explained in detail in next

section.

2.2 Test Automation Framework Components:

2.2.1 Generic/Common Libraries:

This component will contain reusable functions for basic controls operations, Error
handling and error log functions. These basic functions will be used in Application
specific function libraries and automated scripts.

Wipro Technologies Confidential Page 9 of 35

 Test Automation Framework BNYM - WIPRO

Some of the functions that act on controls/objects of the application like text box,
check box, radio button, window etc. are given below.

Sl.
Function
No Description Input Parameters
Name
.
1 invoke_URL Function to invoke the web application Bank Of Newyork URL
having the URL as a reference Address
2 fnc_wait Function To wait for a object in the Object Name
application
3 Login Function for logging onto the Username and Password
application.
4 logoutfromAp Function for log out from the BrowserName, PageName
p application
5 FormatInput Function for removing the blank spaces param_array - an array of
and converting the string to lower case parameters
6 Click_WebEle Function for clicking on the Objects on Browser Name, PageName,
ment the web page WebElement Nam
7 Select_Menu Selecting the Menu by passing the Browser Name, PageName,
menu path ( ; is delimitter) WebElement Name
8 Click_Button Function to check if a Web button is BrowserName, PageName
enabled or disabled and Button name
9 set_WebEdit_ Function to check if a string value can BrowserName, PageName ,
Value be entered in an edit box Editbox name and Value
10 select_Comb Function to check if value can be BrowserName, PageName ,
o_Value selected in a combo box combobox name , select
value
11 get_WebElem BrowserName, PageName Getting the data from a
entData Webtablename, Row,Column web table
12 compare_Mes Functtion to check if two messages Message 1 and Message 2
sage are matching or not
13 verify_WebTa to check if the error message displayed BrowserName, PageName ,
ble_Validatio is correct and has all the mandatory WebTable name and Error
nMessage fields to be filled Message to be verify
14 get_WebEdit Function to check if tvalue can be BrowserName, PageName
_Value taken from an edit box and Editbox name
15 click_Image Function to check if the image can be BrowserName, PageName
clicked on a web page and Image name
16 validate_Che Function to c heck if a check box can BrowserName, PageName
ckbox be selected or not and Checkbox name
17 select_Check Function to select a checkbox BrowserName, PageName
box and Checkbox name
18 ExecutionLog This function is to Delete the execution <filespec> filename path
FileDelete file
19 Execution_lo This function is to capture the a) <iStatusLevel> Name of
g execution results. the browser as specified in
application map
b) <sMessage> The
Message to specify what
exactly happens at that
point of time.

Wipro Technologies Confidential Page 10 of 35

 Test Automation Framework BNYM - WIPRO

Sl.
Function
No Description Input Parameters
Name
.
c) <iStatusLevel> Result of
the current Execution.
20 Verify_Flag Verify Flag image is existing or not BrowserName, PageName
and Image name
21 Verify_FlagN Verify Flag image is existing or not BrowserName, PageName
otExists and Image name
22 captureScree This function is to capture the Nil
nshot screenshot of the error.
23 createAlphan This function is used to Create Random <intsSize>: The Size or
umericString AlphanumericString length of the generated
String
24 closeInternet This function is to closing unexpected BrowserName, PageName
Exp_Window internet Explorer window and ButtonName
25 CreateRando This function is used to Create Random <intsSize>: The Size or
mString String length of the generated
String
26 timeDifferenc This function is to identify the a) <strInterval> - Types of
e difference between two dates. interval like "yyyy" for year,
"m" for mpnths and "d" for
days
b) <strDate1 and
strDate2> - Two dates to
compare
27 select_Radio This function is to select a Radio Browser Name, PageName
button Button. and Radiobutton Name
28 add_Number This function is used to Add the intDays ( No of Days to be
ofdays_To_cu Number of Days to the Current Date Added or removed)
rrentDate and it will return the Calculated Date.
29 pageCheck_ This function is to check it the WebEdit BrowserName, PageName
WebEdit Elements are present in the current and WebEdit Elements
Page.
30 pageCheck_ This function is to check it the WebList BrowserName, PageName
WebList Elements are present in the current and WebList Elements
Page
31 pageCheck_ This function is to check it the BrowserName, PageName
WebTable WebTable Elements are present in the and WebTable Elements
current Page.
32 DeletingFile This function is to delete a file if it The Path of the File to be
Exists. deleted
33 chkFileExist This function is to check if a file exists Path of the File to be
in a particular path. Checked
34 operation_on This function is to perform specified BrowserName, PageName,
_FrameObjec operation on object within a frame. FrameName, ObjectType,
ts_WithName ObjectName and Value that
need to be Entered.

Wipro Technologies Confidential Page 11 of 35

 Test Automation Framework BNYM - WIPRO

2.2.2 Application specific Function Library

This will contain the functions specific to Master File and Corporate Actions
application. The different functionalities of the application will be identified and
analyzed. Once different functionalities are identified, the functions/subroutines are
developed for each of the functionality and maintained under respective module
(Master File/Corporate Actions). The automated script will call the appropriate
function based on the test cases.

Some of the functions specific to the ADR Application are listed below.

Sl.
Function
No Description Input Parameters
Name
.
1 chkHomePag Check the ADR home page options BrowserName, PageName
e and Home Page Options
2 chkMFCAPage Check the MasterFile/CorporateActions BrowserName, PageName,
links and Welcome text Link Name and Version
details
3 chkCUSIPRep Check the header names in the Reports BrowserName and
ort PageName
4 chkCUSIPRep Check the four links available in the BrowserName and
ortLinks Report Page PageName
5 chkCUSIPSea Check the fields and values available in BrowserName and
rchCriteria the search criteria table in reports page PageName
6 chkPreDefine Check the fields and values available in BrowserName,PageName,
dReports the search criteria table in reports page Predefined report links
(string format with ;) and
Pre defined link name
7 CUSIPSearch This function is to enter the CUSIP BrowserName, PageName,
Criteria Search criteria WebListNames,WebEditNam
es
8 CUSIPReport This function is to enter the Filter BrowserName,
FilterCriteria Search Criteria PageName,LinkName,WebLi
stNames,WebEditNames
and ButtonName.
9 CUSIPReport This function is to enter the Sort BrowserName,
SortCriteria Search Criteria PageName,WebListNames
and Button Nam
10 CUSIPReport This function is to check for the BrowserName,
Filter_ClkButt existence of the Objects after clicking PageName,LinkName, Table
ons on Add or Delete Button. Name, WebEdit & WebList
Object ClassName and
Button Name.
11 WebElements This function is to get the Child BrowserName,
Count Objects. PageName,Table Name,
Objects ClassName & html
tag Name
12 CUSIPReport This function is to export the BrowserName,

Wipro Technologies Confidential Page 12 of 35

 Test Automation Framework BNYM - WIPRO

Sl.
Function
No Description Input Parameters
Name
.
_SaveExcel CUSIPReport into an Excel by clicking PageName,LinkName and
on the Save as Excel link. the Path where the Report
has to be saved.
13 HOLDRSearc This function is to enter the HOLDR BrowserName, PageName
hReports Search criteria for Reports.
14 SetDate_Hold This function is set the Date by BrowserName, PageName,
rOperation selecting the Date, Month and Year on FrameName, MonthValue,
a Frame Object in Holder Operation YearValue and DateValue
Report and Holdr Client Service Report
for Master File Application.
15 HOLDRSClien This function is to enter the HOLDR BrowserName
tServiceRepo Client Service criteria for Reports.
rts
16 HOLDRSOper This function is to enter the HOLDR BrowserName
ationReports Operation criteria for Reports.

2.2.3 Test Data Files:

The test data component contains input data required for automated test cases. The
test data will be placed in a spread sheet and will be kept out side of the automated
scripts.

The excel sheet will have only input test data. There will not be any excel file created
for output data. Output data here is only the result file, which will be generated after
script execution.

Different excel files will be created for Master File Profile & Reports, Corporate
Actions Profile & Reports and Administration. Inside the excel file, different sheets
will be used for keeping the test data related to different menu items like, Enterprise,
Company, Contacts, DR, etc. All the screens in a particular module/functionality are
to be analyzed and each field (like text box, dropdown list, radio button, check box
etc.) which requires variable data is to be identified. Each identified field will be a
column in the data sheet. The data related to a test case will appear as rows with
test case name.

An illustration of data sheet is given below.

Wipro Technologies Confidential Page 13 of 35

 Test Automation Framework BNYM - WIPRO

A global excel file will be created which will contain list of all the scenarios for Master
File and corporate Actions. This spread sheet serves as configuration/driver file that
specifies the test scenarios to be executed. The main driver script will read the data
from this file and performs the execution accordingly.

A sample is given below.

2.2.4 Functional/Modular Scripts:

This is the main component of the framework that contains the modular scripts for
each scenario of Master File and Corporate Actions. Each modular script will address
the execution of set of test cases related to a particular functionality/scenario of the
application like, CUSIP Search, HOLDR Search, Underlying bulk move, etc. The

Wipro Technologies Confidential Page 14 of 35

 Test Automation Framework BNYM - WIPRO

modular scripts will use the application specific functions to form the scenarios. Each
modular script will read the data from corresponding excel sheet and executes the
test cases based on number of rows present in the test cases.

The automated modular script utilizes all the other components of the framework. A
general flow consists of following steps:
 These modular scripts will be called by Driver Scripts
 Loads the required Object repository, generic and application specific library
and excel file.
 Calls the required functions from Function Library based on the test
case/test scenario.
 Reads the input Test Data from corresponding Excel sheet
 Uses Object Repository to identify the objects of the application and
executes the test cases
 Test execution results will be written to Result Files

Script independency:

Some times, it may require that a test case may have dependency on another test
case. That is, test case ‘abc’ has to be executed before test case ‘xyz’ to meet some
pre-condition. Such kind of requirement calls for logical grouping of test cases that
are to be executed. To handle this situation, the pre-requisites for a test case will be
analyzed. Based on the feasibility, appropriate actions will be taken inside the test
script to meet the pre-requisite. So, entry point and exit point for any test case will
be the same (most of the time starts from login to the application and ends with
logout).

The test cases that are not feasible to execute independently will be analyzed further
and addressed during construction phase.

2.2.5 Driver Scripts:

This component will contain the driver scripts like Master File driver script, Corporate
Actions driver script, etc. Each driver script will call the related Functional/Modular
scripts based on the execution requirement. The scenario execution requirement will

Wipro Technologies Confidential Page 15 of 35

 Test Automation Framework BNYM - WIPRO

be configured in Global/Driver excel file that specifies the scenarios that are to be
executed.

2.2.6 Object Repository:

The primary activity in any Test Automation is building the object repository and
associating it with the test. Here as part of BNYM Automation we will build a Shared
Object Repository and it will have a file extension .tsr (For E.g. MasterFileOR.tsr)

This component of the framework will contain the shared object repository that
stores the description of the ADR application objects like, Internet explorer browser,
page, text box, combo box, radio buttons, etc. This file can be accessed by multiple
test scripts and functions. All the required objects of the application will be added to
the object repository using QTP and the logical names generated by QTP will be
renamed to give meaning full names.

With the use of Shared Object Repository Test object information that applies to
many actions/functions is kept in one central location. When the objects in
application changes, we can update them in one location for all the actions and this
is one of the key advantages of using a shared object repository.

A snapshot of Object Repository is given below.

Wipro Technologies Confidential Page 16 of 35

 Test Automation Framework BNYM - WIPRO

2.2.7 Result Files:

After execution of automated test cases, the script management module will log the
results in this module. This basically acts as a container for test results. Every
verification points should be captured in the test log with the proper pass/fail, error
or warning message. Along with verification point, the actions performed on AUT like,
entering data in text box, selection from list, selecting check box, clicking on button,
etc. will also be captured in result log file.

One of the test report generated from tool is depicted below.

Wipro Technologies Confidential Page 17 of 35

Test Automation Framework BNYM - WIPRO

Wipro Technologies Confidential Page 18 of 35

 Test Automation Framework BNYM - WIPRO

Results File Management:

The file structure for storing the results of different releases for execution cycles is
depicted below.

2.2.8 Project Directory Structure:

Directory structure for Automation is required to Maximize Sharing, Consistency in
the automated script storage and eliminates duplication of efforts. All the Automation
artifacts will be placed in SVN version control tool.

Snapshot of the folder structure at a high level is given below, representing the
organization of automation assets.

Wipro Technologies Confidential Page 19 of 35

 Test Automation Framework BNYM - WIPRO

ADR_Automation Folder:
All the Test Assets will be created and stored under ‘ADR_Automation’ root
folder. Path independent design enables you to place the folder in any path and
can start executing the scripts with little or no modification. The
‘ADR_DriverScript’ is placed under the root folder which will drive the script
execution.

Automation_Scripts Folder:
This folder contains 2 sub-folders, one for placing modular scripts specific to
Master File and the other for Corporate Actions application. Each modular script
will address the execution of set of test cases related to a particular

Wipro Technologies Confidential Page 20 of 35

 Test Automation Framework BNYM - WIPRO

functionality/scenario of the application like, CUSIP Search, HOLDR Search,

Underlying bulk move, etc.

DataTables Folder:
This folder contains the excel files used to store test data related to the
application. Different excel files will be created for Profile and Reports section of
Master File and Corporate Actions. The Automation script will read the data
from respective excel sheet.

Function_Library Folder:
This folder will contain library files (*.vbs) which will have:
(i) Functions specific to Master File and Corporate Actions application.
(ii) Common utility functions and error handling functions used across the
application

Object_repository Folder:
Shared object repository (*.tsr) files will be stored in this folder. A shared
object repository stores test objects in a file that can be accessed by multiple
tests. There will be 2 object repositories one for the objects of Master File and
other for Corporate
Actions.

Results Folder:
After execution, the automated scripts will log the execution results in this
folder. The detailed and summary reports will be placed under this folder.

2.3 Error Handling and Recovery:

The exception handling is broadly classified as follows:

Basic failures:

These are the failures that occur at the system level (e.g. Data Table, Window
declaration file not loaded, library file not found, etc.).

Wipro Technologies Confidential Page 21 of 35

 Test Automation Framework BNYM - WIPRO

Before opening any file, its existence in specified path will be checked. Every function
starts with checking for appropriate window. Utilities are developed for basic
functionalities like filling the text box, selecting radio button and selection from list
box. These utilities will check for existence and enablement of controls before doing
any operations.
If there are any such failures, the script logs appropriate message and continues
execution with next test case/scenario.

Application failures:

Failures corresponding to the application like Unexpected Pop up window, Page Not
found, server time-out etc. falls under this category. These kinds of errors will be
handled by Recovery scenario wizard of QTP. Different exceptions will be captured
and appropriate functions will be developed to handle each scenario. Whenever any
error occurs that interrupt the script execution, QTP automatically calls the recovery
mechanism which in turn calls the function to handle the exception.

Application Log / Result Files:

Under certain erroneous conditions QTP aborts abnormally, closing the test result file
created. Under such circumstances the results of the test run are also lost. To
handle this, an Application Log File can be created to log the test results of the
automation test run. The Format of the Application Log will be Text (.txt).

The results of the last test run can be viewed in this file and it can be saved for
future reference. The name of the log file created can include the name of the test
run, version and build details of the application under test and the date of the
execution of the test. Thus a unique application log file can be created for each test
run.

2.4 Coding Standards:

BNYM_QTP_Coding_
Standards_and_Naming_Conventions V1.0.doc

Wipro Technologies Confidential Page 22 of 35

 Test Automation Framework BNYM - WIPRO

3 Automation Execution Flow:

Automation execution flow diagram is depicted below.

 The driver script will load Object repository, Library files and Master data
sheet.
 Based on the ‘RUN_FLAG’, driver script will invoke appropriate modular
test scripts.
 Each modular test script (scenario like CUSIP search, Underlying bulk
move, etc.) will load the appropriate excel sheet.
 The test script will invoke application under test.

Wipro Technologies Confidential Page 23 of 35

 Test Automation Framework BNYM - WIPRO

 Based on the test script, fetch the appropriate data from the Excel sheet
and key in to the application under test.
 Fetch the Actual value from application under test and verify with the
expected value either in excel sheet or inside the script
 Display the Pass / Fail results or Log messages for each of the test step.
 Result files will be saved in the appropriate folder.

Wipro Technologies Confidential Page 24 of 35

 Test Automation Framework BNYM - WIPRO

4 Re-usability:

The activity of creating the framework (functions and sub-functions) will leverage the
automation scripts. The plan is to re-use the code (in terms of flows), parameterize
and fit it in to the designed framework.

The reusability model contains two major components:

4.1 Common Utility Function Library:

The common utility library contains general functions like filling edit box, selecting
dropdown item, closing all windows, etc. This library will also contain the functions
for generating customized test reports. These functions can be reused while
developing application specific function library as well as in the automated scripts.

Most of the functions in this library can be useful in automation of any application
that uses similar technology.

4.2 Application specific Function Library:

The ADR application and test cases will be analyzed to identify the reusable
functionality. Appropriate functions will be developed for these functionalities that
can be used across whole application to automate test cases. The test script will
actually contains a series of calls to different functions and navigation logic based on
the test case.

4.3 Reusability of Test Data:

The developed automation scripts will support reuse of same test data for repeated
execution cycles, provided there is no changes in the test specification. During
execution, the script checks for the existence of the test data in the application.

Wipro Technologies Confidential Page 25 of 35

 Test Automation Framework BNYM - WIPRO

Appropriate actions will be taken by the script based on the requirement. The
implementation logic is illustrated with an example in the flow chart depicted below.

Figure 1: Test data reusability

The ‘Create User’ procedure will check for the existence of same user. If user already
exists in the application, then the user will be deleted and recreated. In case of
‘Delete User’ procedure, the script checks for existence of user to be deleted. If user
does not exist, then creates the user before performing deletion.

Wipro Technologies Confidential Page 26 of 35

 Test Automation Framework BNYM - WIPRO

5 Extensibility:

Extensibility is one of the important aspects of any Framework. The extensibility of

this automation framework is illustrated below.

Schematic Representation of Framework (Base Model):

This diagram is a schematic representation of the test framework in its entirety. It

focuses on the control flow, with respect to how the test sequence and the test data
are interpreted from the data model.

Wipro Technologies Confidential Page 27 of 35

 Test Automation Framework BNYM - WIPRO

Expansion Strategies – Data Model:

Flow chart given below specifies the strategy for expansion of data model when there
is a new requirement or change in the existing requirements.

Expansion Strategies – Scripts:

Flow chart given below specifies the strategy for expansion of framework scripts
when there is a new requirement or change in the existing requirements.

Wipro Technologies Confidential Page 28 of 35

 Test Automation Framework BNYM - WIPRO

Schematic Representation of Framework (Post expansion):

This diagram is a schematic representation of the test framework in its entirety with
respect to expansion strategy.

Wipro Technologies Confidential Page 29 of 35

Test Automation Framework BNYM - WIPRO

Wipro Technologies Confidential Page 30 of 35

 Test Automation Framework BNYM - WIPRO

6 Configuration Management

This Automation framework will use Subversion (TortoiseSVN), which is an open

source version control system. (The installation and configuration of SVN is out of
scope of this document)

The Flow Chart for Version Controlling and Script Development is given below.

1. Script Design and Development phase:

Resynchronize the Latest

ADR_Automation from the SVN
to the local machine

On the Local Machine, Develop the

scripts and execute the script for 2
times with consistent results

Upload the Test data and the

Script to the existing shared
folder for a Peer Review to be
done

YES
Re m ist
IF iew ts
Co e

Make the Changes as per the Peer

v en
m x

Review Comments

NO

Wipro Technologies Confidential Page 31 of 35

 Test Automation Framework BNYM - WIPRO

2. Integration Phase:

Obtain the Scripts and the Test

Data from shared folder

Move the Test Data (for instance

MasterFileReports.xls) to the
DataTables folder in the Frame
Work. If data requires to be
appended then modify the
existing excel sheet

Get the Object Repository used in the script

and move it to the respective folder. If the
Object Repository already exists then modify
the existing repository

Get the New Functions used in the

Script and move it to the respective VB
script file (say, MasterFileLibrary.vbs).
If the Function already exists then
modify/enhance the existing Function

Update the test script (for

instance “CUSIPReport
Search”) in the respective
folder (e.g.,
Automation_Scripts \
MasterFile_Scripts)

Wipro Technologies Confidential Page 32 of 35

Test Automation Framework BNYM - WIPRO

Submit the integration

for Review

YES
Re m ist
IF iew ts
Co e

Make the Changes as per the Peer

v en
m x

Review Comments

NO

Wipro Technologies Confidential Page 33 of 35

 Test Automation Framework BNYM - WIPRO

3. Execution Phase:

Compile the scripts and check for

the compilation errors

YES Debug and fix

is or
ex err

the Errors
ts
IF

NO

Run the Driver script

(ADR_Automation\ADR_Driver
Sript) for a smoke test

After a consistent set of results are obtained,

check-in the latest Frame work into SVN and
give the Suitable Label for the files checked in.

Wipro Technologies Confidential Page 34 of 35

Test Automation Framework BNYM - WIPRO

This Page is intentionally Left Blank

END OF THE DOCUMENT.

Wipro Technologies Confidential Page 35 of 35