Beruflich Dokumente
Kultur Dokumente
Production Technologies
Number of pages:
Distribution List:
Summary:
Countrywide
Countrywide
1
1. Introduction
Purpose of this document to support and provide required guidelines for a tester to configure and execute
the automation scripts through Quality Center and QTP tool. The topics covered are configuration and
creating test lab in Quality Center, setting runtime and configuration parameters, execution of QTP script
from quality Center and results tracking and analysis.
A user can connect to Quality Center through QTP tools to access the scripts available in the Quality
Center. To connect to Quality Center-
1. Open the QTP from Desktop.
2. Select Quality Center Connection icon from menu bar OR select File->Quality Center Connection menu
item. Quality Center connection popup will be opened.
3. Enter required information to the Quality Center connection wizard like “URL”, “user name”,
“Password” , “Domain” and “Project” and select Login button.
4. Select File->Open OR open icon from menu bar to select a script from Quality Center.
Figure-1
2
2.2 Connecting to Quality Center though web browser interface
User can open Quality Center web interface through the URL http://qualitycenter.
3. Folder Structure
Automation suit code base is available under the Test Plan tab, which consists of three folders those are
1. Development – is a folder where all the development scripts will be located.
2. Handoff – is a folder where all scripts delivered to client will be placed.
3. Performance – is folder has scripts used by performance testing team.
Figure-2
3
Config: Configuration file has the environmental variables of URL, Userid, Password, Pool, Ac-
cessResultsLocation 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.
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
3.2.1 24by7:
A set of scripts have been identified which would be running for 24by7. The main intention of creating this
test set is to cross check whether all the services are up and running.
4
3.3 Performance folder:
These Set of scripts were developed specific to performance testing team which returns the page rendering
time in the application which helps the performance team to evaluate performance of the system.
Click on the Arrow mark in green to send the test script to the Test Set
Close the test plan tree structure
For details refer Figure-3
5
Figure-3
6
Figure- 4
Configuration File
*********************************************************************
Config .ini
*********************************************************************
[Environment]
Url=http://originationit
Userid=
Password=
Pool=A
AccessResultsLocation=agotsnexosdev03\E$\NexOS.Kiran\NEXOS\TestData\NexOSPOS.mdb
Login_conf_path=\\agotsnexosdev03\E$\NexOS.Kiran\NEXOS\Config\Login_config.xls
ScreenshotRootpath=\\agotsnexosdev03\E$\NexOS.Kiran\NEXOS\TestResults\TestSet
POS_Validation = Y
TakeScreenshot = Y
7
***********************************************************************
*
4.4. Execution from Test Lab
Go to Test Lab in Quality Center
Select the required test from the execution grid and click on 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.
Figure- 5
5.1. Reporting
8
5.1.1. 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 : agotsnexosdev03\E$\NexOS.Kiran\NEXOS\TestData\NexOSPOS.mdb
9
Figure- 6
Note: Click on Launch report Button in Test instance Properties Dialog Box for viewing
the QTP generated XML results.
Note: Results can also be tracked from QTP Results tab also. Refer figure- 7
Figure- 7
1
5.2. Screen shots
Screen shots are also taken for the failure of verifications and validations. A function is used in the script to
take screen shot of the failure of verification and validation errors. All the Screenshots are stored in a path
mentioned in Config.ini file where the environmental variable for that path is defined. A function is called
in the script to capture the screen shot and store in the path defined.
Figure- 8
11
1