Test Automation Framework

1. Automation Framework
1

2. Test Automation Approach
 The Test Script Modularity Framework
 The Test Library Architecture Framework
 The Keyword-Driven or Table-Driven Testing
Framework
 The Data-Driven Testing Framework
 The Hybrid Test Automation Framework
2

3. Test Automation Framework
The most commonly implemented framework is a
combination of all of the above techniques, pulling
from their strengths and trying to mitigate their
weaknesses.
NexOS Test Automation Framework (Hybrid) =
Test Script Modularity / Test library Framework
+
The DataDriven Testing Framework
3

4. Test Script Modularity Framework
 The test script modularity framework requires the
creation of small, independent scripts that represent
modules, sections, and functions of the application-
under-test.
 These small scripts are then used in a hierarchical
fashion to construct larger tests, realizing a particular
test case.
4

5. Test Library Architecture Framework
 The test library architecture framework is very similar to the test
script modularity framework and offers the same advantages, but
it divides the application-under-test into procedures and functions
instead of scripts.
 This framework requires the creation of library files (SQABasic
libraries, APIs, DLLs, and such) that represent modules,
sections, and functions of the application-under-test. These
library files are then called directly from the test case script.
 This is incorporated in NexOS Project by creation of Business
functions which are specific to partition/workspace/reveal in vbs
files and NexOS,generic / Global functions (for each web
Object). which are used as libraries.
5

6. VBS files for Partitions
Partition in NexOS Library file
1.Login NexOS_Login.vbs
2.Application NexOS_Application.vbs
3.Credit NexOS_Credit.vbs
4.LPF NexOS_LPF.vbs
5.PRP NexOS_PRP.vbs
6.Registration NexOS_Registration.vbs
7.Underwriting NexOS_Underwriting.vbs
8.Submit NexOS_Submit.vbs
9.Pipeline NexOS_Pipeline.vbs
Each .vbs file has the functions defined for that particular
partition
6

7. VBS files for Generic Functions
Functionality Library File
1.Datatable DataTable.vbs
2.Global Global.vbs
3.Reporting HTML.vbs
4.Object Descriptions Constants.vbs
5.Messages messages.vbs
6.Utilities util.vbs
7

8. Data-Driven Testing Framework
 Data-driven testing framework is incorporated in
NexOS Project by inputting the data into an Excel file
and importing the values into QTP Data table at the
time of execution.
 Enables to test the application with multiple sets of
data.
8

9. Configuration Settings
 Environment Variables (read only data) are declared
in Config.ini file
 Following are the Environment variables:
• AccessResultsLocation
• ScreenshotRootpath
• POS_Validation
• TakeScreenshot
9

10. Login Configuration
 The user id, password (encrypted) and environment
(URL) and the Host Name are driven from the
Login_Config.xls file attached to the config folder in
the QC test plan
 Default URL i.e., http://originationit will be taken if
there is no entry for the URL and the QC User Name
will be taken to login to the application if there is no
userId Provided in the Login_Config.xls file
10

11. Folder Structure
Test Plan consists of three main folders:
Development contain scripts under construction
Test Plan
Handoff are scripts delivered to client.
Performance are scripts modified
for stress testing.
Each folder structure contains:
Config Documents
LIB OR
Recovery Scripts
11

12. Test Plan Structure
 Config: Configuration file has the environmental variables of
URL, Userid, Password, Pool, AccessResultsLocation path,
Login config path, Screenshot root path, POS validation and
Take Screen shot.
 Documents: Documents folder contains all documents required
for preparation and understanding of the NexOS Automation
project.
 LIB: Contains Business Library and Global Library Functions
located in the form of vbs file
 OR: Contains object repository files attached in the Attachment
section. Object Repository is used in Login part of the
application, because some win objects are not identified by the
descriptive programming or takes more time to identify. The file
is saved in .tsr( Test Shared Repository) extension.
12

13. Test Plan Structure (continued)
 Recovery: Contains some attachments for Recovery Scenarios
in .qrs(Quick Test Recovery Scenario) and .vbs files are attached
in Attachment section
 Scripts: Contains Integration and POS folders, where integration
folder contains Test set folder, in Test Set Process Flow folder
wise is divided, respected test scripts and the Smoke Test
Cases. Each test script has its own test data attached in the
attachment section. POS folder contains all the pos test scripts
and the test data attached to the Attachment section.
 The Test Scenarios in NexOS automation Project are divided
into different Test Sets, each Test Set contains 10 Process
Flows, each flow contains different Test scenario Scripts, for
each script test data is attached in the Attachment section.
 Test Set (X)->Process Flow (X)->Test Script
13

14. Handoff and Performance Folder
Handoff folder:
 Folder structure is same as the structure mentioned above
(i.e. Config, Documents, LIB, OR, Recovery, Results and
Scripts).
 Process of delivering the scripts is a folder is created with a
date 2007_11_15(start date of deliverables).
Performance folder:
 These set of scripts were to support performance testing
team and returns the page rendering time.
14

15. Script Components Guideline
When the script is developed and ready for execution,
follow the guidelines given below:
 Connect to Quality Center.
 Ensure that Test Data (Excel sheet) is attached
to the Test Script.
 Add all the Library files required for test
execution in LIB.
 Add Configuration file in Config folder.
 Add Object Repository file in OR.
15

16. Script Execution from Test Lab
 Go to Test Lab in Quality Center
 Select the required test from the execution grid and
click on Run button on the header,
 Select the required host for execution and again click
on Run button in the Pop up window
 Quality Center will initiate QTP and executes the
selected script.
 Click on Run Test Set button in order to run the entire
Test set
16

17. Execution From QualityCenter
17

18. Test Results
Test Results are of two types:
1) Reporting
2) Screen shots
Reporting - Test Results are stored in two places.
 Microsoft Access (Database)
 Test Lab in Quality Center.
Screen shots
18

19. Storing Results in Access and QC
Tracking Results in MS-Access:
 All the Verification points in each script are stored in the
Respective Table of the MS-Access. Results can be tracked at
the following location which can be configurable from the
configuration file.
Path :
agotsnexosdev03E$NexOS.KiranNEXOSTestDataNexOSPO
S.mdb
Test Lab in Quality Center:
 Go to Test Lab Tab in the Quality centre
 Double click on the script executed in the Execution grid
 Double click on the Run Name in the Test instance Properties
Dialog Box
 Verify the results in the Run Steps Dialog box
19

20. QualityCenter Execution Example
20