Nexos Automation User Guide

DCountrywide Production Technologies

NexOS Automation User Guide

Number of pages: Author: Siva Kumar.T

Reviewed by :

Approved by :

Date:

Date:

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.

2. Test Configuration and Management 2.1 Connecting to Quality Center though Quick Test Professional interface A user can connect to Quality Center through QTP tools to access the scripts available in the Quality Center. To connect to Quality Center1. 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.

3.1 NEXOS(Development) folder structure is as below: •

Config

•

Documents

•

LIB

•

OR

•

Recovery

•

Scripts

Figure-2

3

 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.

 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 Handoff folder: •

Handoff folder contains all the deliverables of the project.

•

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).

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.

3.2.2 Smoke Test: A set of scripts have been identified which is used for Smoke Test (which tests most of high level functionality in NexOS application).

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.

4. Execution Guide Lines 4.1 When the script is developed and ready for execution follow the guide lines 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.

4.2 How to pull a Test script to a Test Set in Test Lab?  Create required Test Set

 Click on

button on the header of Execution grid

 Select the required test script from handoff folder in Test Plan tree which is displayed in right side in Test lab

 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

4.3 Steps to configure config.ini file:  Mention\Modify the Url required in the configuration file  Mention\Modify the Userid to be used in the execution  Mention\Modify the Password(Not in use as of now)  Mention\Modify the Pool from which it has to execute  Incase Userid is not mentioned in the Configuration file then the Quality Center user name would be used to login into Application.  Configuration file is not attached to the test set in the Test Lab by default it will take from the Test Plan/ Handoff/ config folder.  While executing make sure that configuration file is attached and configure to Test Set in Test Lab.  Any changes made in configuration file have to be uploaded in Test Lab, which is attached in Test Set Properties tab  For details refer Figure- 4 and Config file mentioned below

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.

 Click on

button in order to run the entire Test set.

Figure- 5

5. Test Results configuration and tracking Test Results are of two types:

 

Reporting Screen shots

5.1. Reporting Test Results are stored in two places as mentioned below:  Microsoft Access (Database)  Test Lab in Quality Center.

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 5.1.2. 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

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