Online Software Training

SAP TAO Training

Presenter Govind QA Lead bgovind.b@gmail.com

www.testing-onlinetraining.com

Agenda
 Prerequisites for TAO 1.0  TAO Architecture overview  Installation  TAO Connection settings  Configuring TAO  Generating components in TAO  Building Test Scripts  Consolidating Test Scripts  Importing and Exporting Components  Executing Tests

TAO workflow

TAO Installation & Configuration

Prerequisites

TAO Installation & Configuration

 Here is a short checklist of the major areas:  SAP TAO Agent for ABAP on the SAP Server  SAP Scripting enabled on the server side using TCode RZ11  On each computer that needs to be set up with TAO:  Client modules for HP Quality Center.  QTP and the requisite add-ins & patches  SAP TAO Runtime Library (RTL)  SAP TAO Client  Valid SAP TAO license key  UI Scanner  SAP GUI with Scripting Installed  Scripting enabled on SAP GUI client side.

 In addition to the software Installation and Configuration, you will need to import the Component Library into Quality Center for the first time.  The Component Library is a set of Custom Components created for interfacing with the SAP GUI and is located within the SAP TAO Run Time Library (RTL)  You will need to use the SAP TAO Import/Export tool to import these components from the RTL to Quality Center.

SAP TAO Components

 TAO Agent - ABAP based component that resides on your SAP ERP server, called SAP TAO Agent for ABAP  TAO RTL - Contains Business Process Components that has to be uploaded to QC in order to build Business Process Tests in QC  TAO Client - TAO Front end  UI Scanner - It is an add-on for QTP. It scans most of the data in the screen and creates component

Installing the SAP TAO Runtime Library (RTL)

A Run-time library provides special business process testing components for use with the HP Quality Center. This library should reside on a shared drive that all Quality Center clients can access. This installation has to be done in the system where quality center server resides.  To be installed on QC server: 
 Install RTL on the machine where the Quality Center server resides.  Execute the TAORTL Setup from the zip file downloaded from service marketplace.  Specify a directory to install the installation. The default directory is: C:\Program Files\SAP\SAP TAO Runtime Library (RTL).  Make the directory a shared folder and map into Drive X and provide access for all SAP TAO client systems.

 On local TAO client system:  X drive on the local system should be mapped to the shared folder (RTL) on the QC server.

Installing the UI Scanner

 The UI scanner scans most of the data in a UI screen, including dynamically generated objects. It then imports the screen information to the HP Quality Center, where it adds the data to a specified test script.  To install the UI Scanner:  1. Open QTP.  2. Navigate to File>Import Test from Zip File.  3. Browse to the file where you installed the SAP TAO Client (C:\Program Files\SAP\SAP TAO) and select the UI Scanner zip file.  4.The UI Scanner text opens in a blank test in QTP.  5. In the code, please change TAOPATH as SAPTAO exe file location. Ex: TAOPATH = """C:\Program Files\SAP\SAP TAO\SAPTAO.EXE""  5. Save the blank test.

SAP TAO Architecture

Installing the SAP TAO Runtime Library (RTL)

 A Run-time library provides special business process testing components for use with the HP Quality Center. This library should reside on a shared drive that all Quality Center clients can access. This installation has to be done in the system where quality center server resides. To be installed on QC server:
1. Install RTL on the machine where the Quality Center server resides. 2. Execute the TAORTL Setup from the zip file downloaded from service marketplace. 3. Specify a directory to install the installation. The default directory is: C:\Program Files\SAP\SAP TAO Runtime Library (RTL). 4. Make the directory a shared folder and map into Drive X and provide access for all SAP TAO client systems.

On local TAO client system:

X drive on the local system should be mapped to the shared folder (RTL) on the QC server.

Installing the UI Scanner

The UI scanner scans most of the data in a UI screen, including dynamically generated objects. It then imports the screen information to the HP Quality Center, where it adds the data to a specified test script. To install the UI Scanner: 1. Open QTP. 2. Navigate to File>Import Test from Zip File. 3. Browse to the file where you installed the SAP TAO Client (C:\Program Files\SAP\SAP TAO) and select the UI Scanner zip file. 4.The UI Scanner text opens in a blank test in QTP. 5. In the code, please change TAOPATH as SAPTAO exe file location. Ex: TAOPATH = """C:\Program Files\SAP\SAP TAO\SAPTAO.EXE"" 5. Save the blank test.

TAO Installation & Configuration

  Launch the SAP TAO client. Navigate to the Connect window from the hand menu bar.

icon on the left

TAO Installation & Configuration

3. On the right hand side, fill in the information for your QC Server, User, and Password. Click Login. Fill in Domain and Project, and Save. Click on the Connect to Project button. Verify that you see Connected to Project

TAO Installation & Configuration

Available TAO Configuration settings are Inspect Import and Export Consolidate Log License Expert Settings

4. Navigate to the Configuration link on the top right menu. 5. Select the Import/Export tab 6. Under Local Components Path: navigate to the location of the RTL Component Library and click on the Save button.

TAO Installation & Configuration

TAO Installation & Configuration

Navigate to the Import/Export tool from the left hand menu: 8. Select the top level Components folder under Export test components to Quality Center, and click on the Export to QC button.

TAO Installation & Configuration

9. Ensure that you can see these Components in Quality Center.

Component Library:  Buttons Body Screen Buttons  Header buttons Application Toolbar Standard Toolbar Common Functions Actions GUI Functions Buttons Text_Box Verifications

TAO Installation & Configuration

Buttons
Standard Toolbar

Allication ToolBar

Body Screen Buttons

Script Validation

Script Validation
Before you begin automating the test case,  Test Case validation Ensure that you are accessing the correct system and client Ensure that you are able to follow the test case flow Ensure that the test case is detailed enough and resolve any questions you have with the flow.  Data validation Ensure the data provided is working with the test case flow in the system and client you will be using to test. After you validate the test case, you are ready to create the Transaction Components associated with the test case.

Create Components

Create Components
There are 2 ways to automatically create components: 1. Inspect tool:  Enables you to select multiple SAPGUI screens and transactions for testing in an easy to use interface.  It then determines whether these screens and transactions are valid and sends the valid screens to HP Quality Center. 2. UI Scanner:  a plug-in module for HP QuickTest Professional, enables you to collect information from one screen at a time, and sends the screen objects to HP Quality Center as a component. The UI Scanner scans all objects in the screen including dynamically generated objects.

Create Components: Inspect Tool

Using the Inspect Tool: A. Connect B. Configure C. Inspect A. Connection: On the left hand side, highlight your SAP Server and fill in the Client, UserID, and Password information. Click on the Test SAP Connection button to ensure you can connect to the server, the click on the Save button. Now you are ready to use the Inspection Tool.

Create Components: Inspect Tool

B. Configuration 1.Click on the Configuration link on the top right hand corner. Here you can specify:  Generate Components to Local Path  Upload Components to QC automatically  Specify the component path to save to.

Create Components: Inspect Tool

C. Inspection
1. On the Left hand Menu, click on the Inspect button 2. Once on the Inspect Tool screen, click on the Add button to add a Transaction to be inspected. A screen will pop up and allow you to type in the Transaction Code. In the example, we use VA01, and click on the OK button.

Create Components: Inspect Tool

3. You should see a populated list of rows on the table on the right hand side. These rows represent screens configured in the system that are part of the TCode. For example, VA01 has 283 Screens that we can inspect.

Add T-Codes

Choose SAPGUI Dynpros Inspect

Create Components: Inspect Tool

4.You can either select the screens individually by clicking on the checkbox on that particular row, or the select all button . 5.After you have made your selection, click on the Inspect button:

Create Components: Inspect Tool

6.You can view the log by clicking on the View Report link. Here is an example of how the report may look like:

 If screens fail the inspection method, we recommend you use the UI Scanner to scan those screens.  Though you can see which screens have been imported through the Report, be sure to check in Quality Center to validate that the components have been created and imported.  The naming convention of the Component created in Quality Center for the Inspector is: TCode_ScreenNumber_Name Eg. VA01_0101_SalesdocInitialscreenCreate

Create Components: Inspect Tool

Create Components: Inspect Tool

Create Components: UI Scanner

A. Open UI Scanner Script B. Setup C. Execute UI Scanner against any SAP screen(s). A. Open UI Scanner 1. Open up Quick Test Professional. 2. Navigate to File>Import Test from Zip File 3. Browse to the path where you installed the SAP TAO Client (C:/Program Files\SAP\SAPTAO Runtime Library (RTL)) and select the UI Scanner zip file. 4. The UI Scanner code opens in a blank test in QTP. 5. In the UI Scanner code, change TAOPATH to SAPTAO.exe on line example: C:\Program Files\SAP\SAP TAO\SAPTAO.exe 6. Create a Folder on the shared X: drive as UI Scanner 7. Save the UI Scanner code as a QTP test on the shared Drive X:\UI_Scanner\ **These steps only need to performed once as you will be able to open the UI Scanner directly from the X drive location here on forward.

Create Components: UI Scanner

B. Setup 1. There are 5 setup parameters you can use depending on your specific needs:

Create Components: UI Scanner

C.Scanning 1. The UI scanner extractor allows the automatic generation of a component for a screen displayed by an SAP transaction 2. Open up Quick test Professional. 3. Open the UI Scanner you saved in earlier steps. 4. Login to the SAP Gui. 5. Navigate to the SAP screen you want to scan. 6. Execute the UI Scanner script with the SAP Screen Active 7. You should be able to see each field highlighted as the script is scanning through the screen. 8. When you see the popup screen with the button Done, click on the button. 9. You can repeat steps 5- 8 until you are done scanning the screens for your test. 10. The names of the component files have the same name as the screens name except for special characters such as :,(,), etc. For example, if the screens name is Create Sales Order: Initial Screen then the name of the generated component will be Create Sales Order Initial Screen. After you create the components either via the Inspect tool or the UI Scanner, you are ready to create the Test Case in Quality Center.

Import/Export Components

TAO Generated Components

Components in QC

Select and Export

Create Test

Create Test
This section will outline the steps a tester should perform in order to create a Business Process Test script. 1. Navigate to the Test Plan module in Quality Center.

The Quality Center Test Plan module

Create Test
2. Select the appropriate folder from the folder tree and create a new blank test. This is done either by clicking the New Test button above the test plan tree or by right clicking on a folder in the Test Plan tree and selecting New Test. New Test button 3. In the Create New Test pop-up window. The name given to the test should correspond with the business process naming convention used. For example,
TS004.01.VA01_Create Sales Order.

Create Test
4. Navigate to the Details tab if it is not already selected. The Details tab should contain information on the test, the most important of which is the description of what the test process is. Other information that should be added includes notes for other testers developing similar scripts, or special execution conditions that someone executing the test would need to watch out for. Any data requirements should also be included here. Attached is an example:
Details Example

5. Navigate to the Test Script view tab. This is where the BPT test will be built out using Business Components. 6. Click the Select Component button, located in the upper left corner of the Test Script view, to display the Component Tree on the right side of the screen.

Select Component button

Create Test
7. Locate and drag the necessary components across from the component folder tree into the test script.

Create Test
8. Set the necessary parameters values. Each component dragged into the Test Script area will show its list of parameters under the Input column. Clicking these parameter links brings up the dialog box as shown below, where values can be set for each parameter. Leave blank any parameters that will not be used by the script.

Create Test

 To the right is a sample outline of the components you would use for a simple VA01 test.  The next slides will walk you through step by step in creating this test script.

Create Test

After you create the test script, you are ready to Consolidate the test script.

Consolidate

Consolidate
 Executing a script in this state will be time consuming, since each component needs to be loaded separately, and the libraries are loaded for every single component.  In order to optimize the execution time, we need to use the Consolidator.  The Consolidator takes a Test Script, and generates a master component that includes all the QTP code of every component, into a single one.  Quality Center, using QTP, only loads the libraries a single time, at the beginning of the component, and then executes the whole set of instructions without switching between components.

Consolidate
1. Open the TAO Client 2. Navigate to the Consolidate screen by clicking on the Consolidate button on the left hand menu. 3. Navigate to your test case and select the test case. 4. Click on the Consolidate button.

Consolidate
 Once created, the Master Component can be found in the Business Components tree, in the Business Components module of QC.  In order to execute the test, it is necessary to create a new Test Script in the Test Plan, having the Master Component as its only component.  Use this newly created test to execute the Business Process in the Test Lab module.
After you consolidate the test case, you are ready to execute the test case in Quality Center.

Execute Test

Execute Test
1. In Qualtiy Center, navigate to the Test Lab. 2. Navigate to the Test Set and add your Test Case to the existing Test Set. 3. Select the Test Case and click on the Run button. 4. Click Run again to execute the test.

Execute Test
Even though creating Business Processes Test Script using TAO might seem like a simple task, there are multiple factors and caveats that need to be taken into account: 1. The initial Components base might prove complete for some BPs, but there will surely be the need to create new components in order to complete all the scripts. 2. Though the UI Scanner will automatically generate the required components, it might be required to manually modify the QTP code, or even to manually create a whole component. 3. VB Script knowledge is welcomed, since sometimes, there might even be the need to create new functions in the libraries, or modify the existing ones. 4. Make sure you always use the most up to date versions of the BCIE, UI Scanner and Consolidator tools. 5. Before starting the scripting, try to manually navigate the Business Process, so every step involved is clear and complete.

Execute Test

We can parameterize data in three ways: In the Business Component. In the script directly. In a data table 1. Use MS Excel to create a data table 2. For every field in the component, create a column with name DT_<variable_name>. This variable name should match the name of the parameter that was specified in the component 3. Save the file in a folder 4. Point the data table path in the Initialize script prebuilt component to the file created in steps 1-3.

Online Software Testing Training

Thank you! Govind

Mail to : bgovind.b@gmail.com www.testing.onlinetraining.com