Sap Tao User Guide

5/13/2018 Sap Tao User Guide - slidepdf.com

http://slidepdf.com/reader/full/sap-tao-user-guide 1/45

User Guide

SAP® Tes t

Ac c e lerat ion and

Opt imizat ion

1.0.10Target Audience

Quality administrators

Application testers

Document version: 1.0 – August 7, 2008



© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,

OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,

Power Architecture, POWER6+, POWER6, POWER5+, POWER5,

POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System

Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,

OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,

WebSphere, Netfinity, Tivoli and Informix are trademarks or

registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is

only to be used by SAP’s Support Services and may not be

modified or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http : / /serv ice.sap.com/ins tgu ides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap .com

http://service.sap.com/instguides

http://www.sap.com/

http://www.sap.com/

http://www.sap.com/

http://service.sap.com/instguides



Term s for Inc luded Open

Source Sof tw areThis SAP software contains also the third party open

source software products listed below. Please note that for

these third party products the following special terms andconditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

Part of the software embedded in this product is gSOAP

software. Portions created by gSOAP are Copyright

(C) 2001-2004 Robert A. van Engelen, Genivia inc. All

Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART

PROVIDED BY GENIVIA INC AND ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN

NO EVENT SHALL THE AUTHOR BE LIABLE

FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED

AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY

OF SUCH DAMAGE.

3. SAP License Agreement for STLport

SAP License Agreement for STLPort between

SAP Aktiengesellschaft

Systems, Applications, Products in Data Processing

Neurottstrasse 16

69190 Walldorf, Germany

(hereinafter: SAP)

and

you

(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive,

non-transferrable, royalty-free license to use

the STLport.org C++ library (STLport) and its

documentation without fee.

B) By downloading, using, or copying STLport orany portion thereof Customer agrees to abide

by the intellectual property laws, and to all of

the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled

with STLport (whether original or modified)

without any royalties or restrictions.

D) Customer shall maintain the following

copyright and permissions notices on STLport

sources and its documentation unchanged:

Copyright 2001 SAP AG

E) The Customer may distribute original or

modified STLport sources, provided that:

o The conditions indicated in the above

permissions notice are met;

o The following copyright notices are retained

when present, and conditions provided in

accompanying permission notices are met:

Coypright 1994 Hewlett-Packard

Company

Copyright 1996,97 Silicon Graphics

Computer Systems Inc.

Copyright 1997 Moscow Center for

SPARC Technology.

Copyright 1999,2000 Boris Fomitchev

Copyright 2001 SAP AG

Permission to use, copy, modify, distribute and

sell this software and its documentation for

any purposes is hereby granted without fee,

provided that the above copyright notice appear

in all copies and that both that copyright notice

and this permission notice appear in supporting

documentation. Hewlett-Packard Company

makes no representations about the suitability

of this software for any purpose. It is provided

“as is” without express or implied warranty.




sell this software and its documentation for any

purpose is hereby granted without fee, provided

that the above copyright notice appear in all

copies and that both that copyright notice and

this permission notice appear in supporting

documentation. Silicon Graphics makes norepresentations about the suitability of this

software for any purpose. It is provided “as is”

without express or implied warranty.


sell this software and its documentation for

any purposes is hereby granted without fee,

provided that the above copyright notice appear

in all copies and that both that copyright notice

and this permission notice appear in supporting

documentation. Moscow Center for SPARC

makes no representations about the suitability

of this software for any purpose. It is provided

“as is” without express or implied warranty.

Boris Fomitchev makes no representations

about the suitability of this software for any

purpose. This material is provided "as is", with

absolutely no warranty expressed or implied.

Any use is at your own risk. Permission to

use or copy this software for any purpose is

hereby granted without fee, provided the above

notices are retained on all copies. Permission

to modify the code and to distribute modified

code is granted, provided the above notices

are retained, and a notice that the code was

modified is included with the above copyright

notice.

Permission to use, copy, modify, distribute

and sell this software and its documentation

for any purposes is hereby granted without

fee, provided that the above copyright notice

appear in all copies and that both that copyright

notice and this permission notice appear in

supporting documentation. SAP makes no

representations about the suitability of this

software for any purpose. It is provided with a

limited warranty and liability as set forth in the

License Agreement distributed with this copy.

SAP offers this liability and warranty obligations

only towards its customers and only referring

to its modifications.

b) Support and Maintenance

SAP does not provide software maintenance for theSTLport. Software maintenance of the STLport

therefore shall be not included.

All other services shall be charged according to the

rates for services quoted in the SAP List of Prices

and Conditions and shall be subject to a separate

contract.

c) Exclusion of warranty

As the STLport is transferred to the Customer on a

loan basis and free of charge, SAP cannot guarantee

that the STLport is error-free, without material

defects or suitable for a specific application under

third-party rights. Technical data, sales brochures,

advertising text and quality descriptions produced

by SAP do not indicate any assurance of particular

attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only

be liable for damage, including unauthorized

operation, if this (i) can be compensated under

the Product Liability Act or (ii) if caused due to

gross negligence or intent by SAP or (iii) if based

on the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent

caused by employees who are neither agents or

managerial employees of SAP, the total liability

for such damage and a maximum limit on the

scope of any such damage shall depend on

the extent to which its occurrence ought to

have anticipated by SAP when concluding the

contract, due to the circumstances known to

it at that point in time representing a typical

transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not

be liable for indirect damage, consequential

damage caused by a defect or lost profit.



D) SAP and the Customer agree that the typical

foreseeable extent of damage shall under no

circumstances exceed EUR 5,000.

E) The Customer shall t ake adequate measures

for the protection of data and programs, in

particular by making backup copies at the

minimum intervals recommended by SAP. SAPshall not be liable for the loss of data and its

recovery, notwithstanding the other limitations

of the present Art. 4 if this loss could have been

avoided by observing this obligation.

F) The exclusion or the limitation of claims in

accordance with the present Art. 4 includes

claims against employees or agents of SAP.

4. Adobe Document Services

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either registered trademarks or trademarks of

Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party

software delivered with Adobe document services and

Adobe LiveCycle Designer, see SAP Note 854621.



Typographic Convent ions

Type Style Description

Example Text Words or characters quotedfrom the screen. These includefield names, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, tablenames, and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Example text Output on the screen. This

includes file and directorynames and their paths,messages, names of variablesand parameters, source text,and names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example

text>Variable user entry. Anglebrackets indicate that you

replace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

I cons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAPLibrary documentation to help youidentify different types of information ata glance. For more information, see

Help on Help General Information Classes and Information Classes for Business Information Warehouse onthe first page of any version of SAP Library .



<August 2008> 7

Contents

1 Introduction .............................................................................9

1.1 About this Document ............................................................................. 91.2 Before You Start ................................................................................. 121.2.1 SAP Notes for the Installation.......................................................... 121.2.2 Information Available in SAP Service Marketplace........................ 13

2 Installation ...........................................................................142.1 Installing SAP Test Acceleration and Optimization Client ...............162.2 Installing SAP Test Acceleration and Optimization RuntimeLibrary (RTL) Parts ................................................................................. 192.3 Licensing SAP Test Acceleration and Optimization .........................202.4 Settings in SAP Quality Center ........................................................... 21

3 Connections ...........................................................................233.1 Connecting the SAP Server................................................................. 233.2 Connecting the SAP Quality Center Server .......................................23

4 Additional Information......................................................................254.1 Configuration of SAP Test Acceleration and Optimization .............. 254.1.1 Self Test ................................................................................. 254.1.2 Inspection Options............................................................................ 254.1.3 Import/Export Options ...................................................................... 254.1.4 Consolidate Options ......................................................................... 264.1.5 Logging Options................................................................................ 26

4.1.6 Expert Settings ................................................................................. 274.2 Working with SAP Test Acceleration and Optimization (Hints andFAQ) ................................................................................. 274.2.1 Usage of SAP Quality Center/QuickTest Professional OutputParameters ................................................................................. 274.2.2 SAP Test Acceleration and Optimization Inspection ..................... 274.2.3 Performance during Test Execution................................................ 284.2.4 SAP Test Acceleration and Optimization/UI Scanner notcapturing Grid Tables ................................................................................ 284.2.5 How to Create own Components using SAP Test Accelerationand Optimization ................................................................................. 28

4.2.6 SAP GUI Window Change Size on Execution................................. 294.2.7 Overwrite Prompt in BCIE................................................................. 294.2.8 Record Number ................................................................................. 294.2.9 Character Removal from Test Plan Name ....................................... 304.2.10 Creating GET Components............................................................. 304.2.11 SAP Quality Center Required Settings.......................................... 314.2.12 Setup Options ................................................................................. 31



Installation Guide: SAP Test Acceleration and Optimization

8 <August 2008>

4.2.13 Consolidator Notes ......................................................................... 324.2.14 After-Installation Notes................................................................... 324.2.15 Changing the Log File Path............................................................ 324.2.16 Component Folder inside SAP Quality Center ............................. 33

4.3 Working with QuickTest Professional (Hints and FAQ).................... 344.3.1 QuickTest Professional Required Patches ..................................... 344.3.2 Creating an Application Area in QuickTest Professional .............. 34

5 Typical Use Cases ...........................................................................355.1 Inspection ................................................................................. 355.1.1 About Inspection............................................................................... 355.1.2 Using Inspection to Select Transactions ........................................355.1.3 Add a Transaction ............................................................................. 355.1.4 Remove a Transaction ...................................................................... 365.1.5 Perform Inspection............................................................................ 36

5.1.6 Using the UI Scanner ........................................................................ 385.2 Building Test Scripts in SAP Quality Center...................................... 395.2.1 Logging onto SAP Quality Center.................................................... 395.2.2 Building a Test Script .......................................................................395.2.3 Parameterizing the Elements ........................................................... 405.3 Consolidating Test Scripts in SAP Quality Center ............................ 415.3.1 Consolidating Test Plans.................................................................. 415.3.2 Consolidating Selected Components.............................................. 425.4 Importing and Exporting Components............................................... 435.4.1 Exporting Test Components ............................................................ 435.4.2. Importing Test Components............................................................ 44



1 Introduction

<August 2008> 9

1 IntroductionThis guide describes the installation and first steps in the usage of SAP Test Accelerationand Optimization (SAP TAO).

1.1 About this Document

PurposeThe highly secure and mission-critical nature of enterprise resource planning (ERP) datameans that customers need to regularly test ERP applications and business processes. ManySAP customers use customized manual procedures to test processes and applications atgreat expense to the company. Manual testing is time-consuming and frequently requires ateam of experienced quality assurance (QA) professionals. In addition, subject matter expertsoften devote extra hours communicating the process data flow to the testers.The SAP Test Acceleration and Optimization (SAP TAO) application streamlines the creationand maintenance of ERP business process testing.

SAP Test Acceleration and Optimization helps QA specialists to break down an applicationinto components which are:

Assembled into test cases through a simple interface using drag and drop Parameterized for flexible reuse, such as reusing a test that has updated data inputs Maintained easily and inexpensively, even when screens, flows, or service packs

change.

SAP Test Acceleration and Optimization is designed for SAP-GUI-based applications. SAPTest Acceleration and Optimization users should be experienced quality administrators whoare familiar with the SAP Quality Center application by HP (also referred to as HP QualityCenter), SAP GUI ERP applications, and business process testing.

Automated testing with SAP Test Acceleration and Optimization maximizes: Testing Deployment

SAP Test Acceleration and Optimization, in tandem with SAP Quality Center,dramatically reduces the amount of time required to build and execute test scripts.

ReuseSAP Test Acceleration and Optimization eliminates the need to create new testswhenever a component changes. If one component changes in a group of tests, justreplace that component and then re-consolidate the tests.

MaintenanceSAP Test Acceleration and Optimization allows you to record componentparameters. SAP Test Acceleration and Optimization provides a Microsoft Excelspreadsheet to save parameters for reuse and maintenance. You can also movecomponents from SAP Quality Center to SAP Test Acceleration and Optimization foradditional backup possibilities.

RobustnessThe SAP Test Acceleration and Optimization inspection process ensures that SAPTest Acceleration and Optimization tests are more robust during changes. Inspectionexamines the data content within a component, not just the screen object behavior.



1 Introduction

10 <August 2008>

IntegrationThe SAP Test Acceleration and Optimization application requires products from SAP and theSAP Quality Center.

Functional BlocksThe SAP Test Acceleration and Optimization client application runs on a Windows system. Itperforms three key functions: Inspecting transactions from a SAP server, exporting thetransactions to SAP Quality Center, and consolidating components or scripts from SAPQuality Center.

InspectionInspection captures the data in a screen or transaction and determines its validity. Itenables you to create and maintain a list of transactions and screens and to add anddelete transactions from this list.

The SAP Test Acceleration and Optimization application provides two modes of

inspection:o The Inspect screen in the SAP Test Acceleration and Optimization clientenables you to select multiple SAP GUI screens and transactions for testingin an easy to use interface. It then determines whether these screens andtransactions are valid and sends the valid screens to SAP Quality Center.

o The UI Scanner, enables you to collect information from one screen at atime, and sends the screen objects to SAP Quality Center as a component.The UI Scanner scans all objects in the screen including dynamicallygenerated objects. The UI Scanner need a running QickTest Professional(QTP) installation on your local workstation.

Import/ExportImport/Export primarily runs in background mode to export and import data from the

SAP Test Acceleration and Optimization client to the SAP Quality Center. However, itis also helpful for maintenance functions, such as moving components from server toserver or from project to projects. The Import/Export module performs the followingfunctions:

Exports components from the Inspector in the SAP Test Acceleration andOptimization client to SAP Quality Center

Imports components from SAP Quality Center to the SAP Test Acceleration andOptimization client

Exports a component from the UI Scanner and sends it to SAP Quality Center inbackground mode

ConsolidationConsolidate gathers all the objects and data in an SAP Quality Center test script andcreates a single component. If you reconsolidate this component, you have acomponent that contains all the code in the test script and other components, butexecutes much faster than the individual components. These “super components”help you maintain business processes. To update one parameter in a process,changes, change the parameter in the component, reconsolidate, and reexecute thecomponent.



1 Introduction

<August 2008> 11

Technical Components SAP Server

The SAP R/3 or ERP (version 46c or later) server stores screens and transactionmetadata, which the Inspector leverages against SAP Quality Center components.

SAP Quality CenterThe SAP Test Acceleration and Optimization application uses the followingcomponents from SAP Quality Center:

o SAP Quality CenterSAP Quality Center is a complete system for automated and manual testing.It enables both non-professionals and QA experts to streamline testing SAPapplications and business processes. It reduces test maintenance andsimplifies test creation with drag and drop functionality. Together, with theSAP R/3 server and SAP Test Acceleration and Optimization, it creates acomplete automated testing environment.

o QuickTest Professional

QuickTest Professional is an automated test solution for functional andbusiness process applications. It captures, verifies, and replays userinteractions automatically. SAP Test Acceleration and Optimization leveragesQuickTest Professional recording features with the UI Scanner. QuickTestProfessional is also required t o execute testing scripts in SAP QualityCenter.

Typical Use caseThis section describes how to test a simple business process with SAP Test Acceleration andOptimization and SAP Quality Center. It assumes that you can access a SAP back endserver that executes the business process transactions you are testing, access to SAPQuality Center, and a properly installed and connected SAP Test Acceleration and

Optimization client on your desktop. For greater detail on installing and connecting SAP TestAcceleration and Optimization see Chapter 2 , “Installation” , and Chapter 3 , “Connections.”

1. Discuss the process flow with the subject matter expert.

2. Create a business process test case with detailed steps.

3. Run the steps manually within the test application to make sure the application generateswithout errors or warning messages.

4. In the SAP Test Acceleration and Optimization client, use the Inspector to specify thetransactions that you need to create a test script. Add other transactions as needed.

5. Open SAP Quality Center to view the list of your selected components.

a. Drag and drop the transactions in the order that they occur in the businessprocess.

b. SAP Quality Center includes a list of common screen commands, such as Open,Enter, and Exit. Move the screen commands using drag and drop as needed.

6. Parameterize the data in the SAP Test Acceleration and Optimization Excel spreadsheetor the SAP Quality Center database.



1 Introduction

12 <August 2008>

7. On SAP Test Acceleration and Optimization, consolidate the data into a single componentthat consists of the transaction code and screen operations.

8. In the SAP Quality Center, create a second business process script using the singlecomponent.

9. Execute the test script and review it for any discrepancies.

10. Save the components in a directory that you can easily access when you need to updatea screen or a transaction.

Constraints

SAP Test Acceleration and Optimization release 1 does only provide direct support for SAPGUI based applications. Using the build-in UI Scanner which is build on top of QuickTestProfessional, you can create SAP Test Acceleration and Optimization compatible testcomponents as well. Because UI Scanner uses QuickTest Professional for screen capturing,many UI techniques can be scanned and evaluated. Following the basic idea of QuickTestProfessional, you can capture UI/screen elements but it depends on the real usecase if thiscapturing can be used to transform it to a test component.

1.2 Before You StartThe following sections provide information about:

SAP Notes for the installation

Information available on SAP Service Marketplace

Naming conventions

1.2.1 SAP Notes for the InstallationYou must read the following SAP Notes before you start the installation. These SAP Notescontain the most recent information on the installation, as well as corrections to theinstallation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in theSAP Service Marketplace at the Internet address:

service.sap.com/notes.

SAP NoteNumber

Title Description

1231935 Installation SAP Test Acceleration andOptimization 1.0.10

Installation note



1 Introduction

<August 2008> 13

1.2.2 Information Available in SAP ServiceMarketplaceInformation on the following areas is available in the SAP Service Marketplace.

General Quick Links

Description Internet Address Title

SAP Notes service.sap.com/notes –

Released platforms service.sap.com/platforms –

System sizing service.sap.com/sizing Quick Sizer tool

Front-end installation service.sap.com/instguides Front End Installation Guide

Security service.sap.com/security –



2 Installation

14 <August 2008>

2 Installation

This chapter is about the installation of SAP Test Acceleration and Optimization on your localworkstation.

Patching from an older version of SAP Test Acceleration andOptimization

The following steps are equal for patching an existing SAP Test Acceleration andOptimization version of you local workstation to the new version.

Before you can install the new version, you have to de-install the old version using thestandard Windows tools.

Please archive or save the working folders under (i.e.) “C:\Program Files\SAP\SAPTAO\WORK”. This folder will not be deleted by the de-installer but will contain technical filesthat were created using the old SAP Test Acceleration and Optimization version. These filesmight not be 100% compatible to the new SAP Test Acceleration and Optimization version.Please follow the same procedure for trace files in the application folder (i.e. “C:\Program

Files\SAP\SAP TAO”).

The recommendation is to de-install the old version and then to rename the application folder(i.e. “C:\Program Files\SAP\SAP TAO”) to something different, that the new SAP TestAcceleration and Optimization will start from a clean environment.

General remark to the uninstalling of SAP Test Acceleration andOptimization:

The Windows-based uninstalling procedure of SAP Test Acceleration and Optimization willrecognize only files that were installed during the initial installation process. The uninstallatingprocess will not remove any files in the “.\WORK” folder. The user specific configuration file(i.e. “C:\Documents and Settings\<user>\Local Settings\ApplicationData\SAP_AG\SAPTAO.exe_Url_<hash>\<version\user.config”) is also not removed. Please

remove these files if you have any security reasons.

Prerequisites for installation

As prerequisites you need:

1.) SAP Test Acceleration and Optimization agent for ABAP

You need the SAP_BASIS component from 46C to 7.10 having a specific supportpackage level. You can simply check for existence of the function module“TMW_TAOAGENT” in your back end systems to determine the correct supportpackage level.

Example: SAP_BASIS 700 needs a SP level of 12.

You need this function module in every back end system that you want to work with.

If your back end system does not have the appropriate support package level, itmight be possible to install the function module as a customer extension. Please getin contact with you local SAP representative.

2.) SAP GUI

You need a valid and running SAP GUI installation of you local workstation.



2 Installation

<August 2008> 15

3.) SAP Solution Manager

SAP Test Acceleration and Optimization needs a connection to a SAP SolutionManager instance (as of SP17) for licensing purposes.

If your SAP Solution Manager is not SP17 it is highly recommended that you updateyour SAP Solution Manager to SP17 or higher.

If this is not possible for any reason please get in contact with you local SAPrepresentative to find a solution for licensing SAP Test Acceleration andOptimization.

4.) SAP Quality Center

You need a running SAP Quality Center instance in your landscape (release 9.0, 9.1,9.2) having the Business Process Testing module installed.

* Quality Center Connectivity add-in

* Quality Center Test Remote Agent add-in

5.) QuickTest Professional

You need to have QickTest Professional (9.0, 9.2, 9.5) installed on your localworkstation. In addition you need to ensure that the following QickTest Professionaladd-ins are installed:

* QuickTest Professional SAP GUI add-in (included in QuickTestProfessional 9.5)

And from Quality Center add-ins page:

* QuickTest Professional add-in

* QuickTest Professional for Business Process Testing add-in

ProcedureThe following list provides the steps and installation requirements to set up SAP TestAcceleration and Optimization.

1. Verify the availablility of the SAP Test Acceleration and Optimization agent for ABAP onthe SAP server or the SAP ERP system.

2. Install the SAP Quality Center API on each computer that will run SAP Test Accelerationand Optimization. The SAP Test Acceleration and Optimization installer checks to see if theSAP Quality Center API has been installed. The installation of the SAP Quality Center API isperformed by connecting and logging in to an SAP Quality Center server.

3. If you plan to execute tests or run the UI Scanner, install QuickTest Professional and the

requisite add-ins on each computer that will run SAP Test Acceleration and Optimization.

4. Distribute the SAP Test Acceleration and Optimization Runtime Library (RTL) on eachcomputer that is configured to execute tests. The SAP TAO RTL is installed during the maininstalltion of SAP Test Acceleration and Optimization.

5. Check the SAP Test Acceleration and Optimization RTL init file (“CBASE_init_vbs”) andadd parameters on SAP Quality Center.



2 Installation

16 <August 2008>

6. Install the SAP Test Acceleration and Optimization on each the system in step 4.

7. To optain a valid license for your SAP Test Acceleration and Optimization installation yousimply can configure the connectivity to an SAP Solution Manager instance in yourlandscape. SAP Test Acceleration and Optimization provides a configuration dialog toadminister this connection.

2.1 Installing SAP Test Acceleration and OptimizationClientThe following instructions assume that you have installed all prerequisistes including the SAPGUI and SAP Quality Center Web access on this system. The SAP Test Acceleration andOptimization installer checks to see if the SAP Quality Center is available.

To install the SAP Test Acceleration and Optimization client on each computer1. Go to the Service Marketplace and download the complete installer file for the SAP TestAcceleration and Optimization client 1.0.10.

2. Run the executable installer file (setup.exe) and accept all the defaults.

SAP Test Acceleration and Optimization can be installed through the network like any msifile, the installation cover in this guide is the standard single client installation.

1. Double click on setup.exe

2. Click Next

3.



2 Installation

<August 2008> 17

4. Select the path where SAP Test Acceleration and Optimization is going to be installed

5. Click Next



2 Installation

18 <August 2008>

6. Confirm your settings by clicking Next

7. At the end of the installation the next pop up will appear

The path that you type on this step is where you can find the shared folder containing theSAP Test Acceleration and Optimization RTL CBASE, LOGS and OBJRef folder

a. NOTE: If this is the first installation this path will be where you will later copy theCBASE folder(see step 2.1.2)



2 Installation

<August 2008> 19

8. The installation of SAP Test Acceleration and Optimization is complete.

2.2 Installing SAP Test Acceleration and OptimizationRuntime Library (RTL) Parts

The following instructions only need to be applied once for each new project (a project isdetermined by a SAP Quality Center project) and only after the first installation of SAP TestAcceleration and Optimization is completed:

1. Once a SAP Test Acceleration and Optimization installation is completed all the Pre-build components will be in the installation folder (i.e. “C:\Program Files\SAP\SAPTAO”) then “COMPONENTS_Default”

a. This folder will be the one that needs to be imported when uploading all thecomponents to start a project

2. Go to the installation folder (by default “C:\Program Files\SAP\SAP TAO”) select thefolder called “CBASE_Default” and copy paste it into the path that you specified instep #6 of the Installation section. This folder could be local or on a central file share.

3. After pasting the folder rename it to CBASE (without the “_Default” string)

The final folder structure should look like this (using default settings):



2 Installation

20 <August 2008>

2.3 Licensing SAP Test Acceleration and OptimizationSAP Test Acceleration and Optimization 1.0.10 presents a different and improved licensingmodel. This model is now server-based where a SAP Solution Manager (having SP17 orhigher) instance will now distribute licenses to the clients. In order to setup this license youwill need to go into configuration.



2 Installation

<August 2008> 21

Here you will find all the available SAP servers on your SAP logon. Provide the correct logininformation. Click the Test SAP connection button. Then click the Check for license buttonand finally Save . Now your local instance of SAP Test Acceleration and Optimization isenabled.

2.4 Settings in SAP Quality CenterThere are some settings to be made in the SAP Quality Center server as well.

Please see the further documentation on the parameter “DISABLE_EXTENDED_STORAGE” mentioned later in this documentation.

In addition you need to upload the file (i.e. “C:\SAPTAORTL\CBASE\CBASE_Init.vbs.txt”) toyour SAP Quality Center. Please refer to the following screen dump for a sample look-a-like:



2 Installation

22 <August 2008>



3 Connections

<August 2008> 23

3 Connections

Use the SAP Test Acceleration and Optimization Connection screen to specify connections toSAP servers and SAP Quality Center server. You must perform these steps on each SAPTest Acceleration and Optimization client.The Connection screen assumes that you can access the SAP server and the server wherethe SAP Quality Center resides. You must know the access paths and passwords for theseservers.

3.1 Connecting the SAP Server1. In the SAP Test Acceleration and Optimization navigation bar, click Connect .

2. On the SAP Logon window, select a server from the list.

3. Complete the following fields:

a. Client – The SAP client number assigned to this server area.b. User ID – The SAP User ID.c. Password – The SAP Password for this user

(The RFC Communication is based on the standard compatible format of passwords:8CHARS (non mixed). Use this format when you create new users or change passwords.)d. Language – The language you want the system to use. SAP Test Acceleration andOptimization supports English (EN).

4. Click Test Connection to SAP to verify the connection.

5. Click Save . SAP Test Acceleration and Optimization remembers the saved connectionsettings the next time you log in.

3.2 Connecting the SAP Quality Center ServerThe right side of the Connect screen provides SAP Quality Center server connections. Toconnect to the SAP Quality Center, at first specify a project and domain and then save theconnection. If you change the connection path, the project, or domain, then you must re-enterand save the new connection information.

1. Click the Connect icon in the SAP Test Acceleration and Optimization navigation bar.

2. On the SAP Quality Center side of the window, complete the following information:a. SAP Quality Center Version – The SAP Quality Center server version number.b. QuickTest Professional Version – The QuickTest Professional version number.c. Server URL – The SAP Quality Center URL.

d. User – The name you use to connect to SAP Quality Center.e. Password – The password you use to connect to SAP Quality Center.f. Domain – The SAP Quality Center domain for your project.g. Project – The first time you connect to SAP Quality Center, accept the default project. SAPQuality Center creates a name for each project you begin and adds the project name to theProject pull-down list.

3. To open a connection to SAP Quality Center, click Log In .



3 Connections

24 <August 2008>

4. Click Save .

5. To open a designated project in SAP Quality Center, click Connect to Project .

6. Click Save . SAP Test Acceleration and Optimization remembers the saved connectionsettings the next time you log in. However, if you want to change the information, enter the

new data and re-click Connect to Project .



3 Connections

<August 2008> 25

4 Additional Information

4.1 Configuration of SAP Test Acceleration and

OptimizationUse the Configuration screen to select settings for the following SAP Test Acceleration andOptimization client functions. To access this screen, click the Configuration link on the upperright corner of the SAP Test Acceleration and Optimization interface. The tabs in theConfiguration screen are:

Self test Inspect Import and Export Consolidate

Log

License (see 2.1.3) Expert Settings

Please check the tool tips for a quick reference to the function.

4.1.1 Self TestUsing the self test function of SAP Test Acceleration and Optimization, you can easily checkfor a correct installation of SAP Test Acceleration and Optimization. Please check for furthernotices in the Info Box (see “Expert Settings”).

4.1.2 Inspection OptionsThe following buttons designate what action the SAP Test Acceleration and Optimizationclient takes when you select transactions:

Generate Components Locally saves components in a specified directory. Use theComponent Location to specify the directory.

Upload the Components to Quality Center moves the components to SAP Quality Centerserver. If you select Generate Components and this setting, the components go to both SAPQuality Center and the specified local directory.

Component Location is the path to the local directory where you want to store savedcomponents.

4.1.3 Import/Export OptionsUse the Import/Export settings to designate a path for transferring components from SAPQuality Center to an SAP Test Acceleration and Optimization client.

Export from is the path where the SAP Quality Center sends components.



3 Connections

26 <August 2008>

Overwrite Components in SAP Quality Center indicates that SAP Test Acceleration andOptimization overwrites a component if it encounters a new component of the same name.

4.1.4 Consolidate OptionsThis screen contains Consolidate and Data Table settings.

Consolidate SettingsCreated in SAP QC Folder –The path to the folder where new components created in SAP

Quality Center are stored.

Overwrite Consolidated – SAP Test Acceleration and Optimization overwrites duplicatecomponents with the most updated data (Default). This step ensures that you do not havecomponents with the same name, but with different data.

Data Table SettingsUpdate the data table file – Select this checkbox to ensure that the data table is updated

automatically.

Enter the Data Table Parameter Prefix – The default data table Prefix is: DT_. Use thisprefix if you intend to save parameters in SAP Quality Center for reuse. SAP TestAcceleration and Optimization creates a database for each script that you build in SAPQuality Center, but only recognizes parameters with the DT_ prefix.

Additional SettingsAdd the component name in consolidated script – SAP Test Acceleration and Optimization

appends the component name to each consolidated test script (Default). Deselect thischeckbox if you do not want to append the component name to each test script.

Prompt for confirmation before consolidating – SAP Test Acceleration and Optimizationdisplays a prompt to consolidate before each it consolidates components. (Default).

4.1.5 Logging OptionsUse the Log Options tab to set log file detail levels and to specify a directory to save files.The log levels are:

0 = None1 = Warning2 = Message and Stack3 = Debug

To specify a log trace levels1. Specify a trace level for each log. The default setting is 1 or Warning.

a. Internal Trace Level

b. SAP TAO Trace Levelc. SAP RFC Trace Level

2. In the Log Location field, specify the path to the directory where you want to save log file.



3 Connections

<August 2008> 27

4.1.6 Expert Settings1. Display Information Box will enable a small information box that will enable you to checkfor further messages of SAP Test Acceleration and Optimization

2. In the Windows Temp text box, you may enter an alternate path to the Windows temp

directory. The default is: “Windows_system_root\temp”.

3. In the SAP Login.ini text box, you may enter an alternate path to the SAP Login.ini file.

4.2 Working with SAP Test Acceleration andOptimization (Hints and FAQ)

4.2.1 Usage of SAP Quality Center/QuickTestProfessional Output ParametersSAP Quality Center and QuickTest Professional provide input and output parameters forpassing data from one component to the other. The SAP Test Acceleration and Optimizationframework only utilizes input parameters and internally determine if the parameter is meant towrite information to the Data Table for other components to use or if the parameter is meantto give an input to the application.

4.2.2 SAP Test Acceleration and OptimizationInspectionSAP Test Acceleration and Optimization is not populating all the screens associated with T-Codes in the Inspect module. There are screens that can be accessed manually, but SAPTest Acceleration and Optimization is not able to display them in Inspect module

As one of the features in SAP Test Acceleration and Optimization, the inspection provides away of automatically generating components by searching in the metadata the information ofthe objects contained in a given screen. This data may be stored in a different format or evennot stored in this metadata at all. This may cause the inspection method to return an errorwhen inspecting certain screens.

Technical Note:

SAP Test Acceleration and Optimization provides different ways to create a screen either byusing the metadata or creating objects during execution (runtime). If an object is displayed ofhidden during runtime then the metadata inspection will not be able to adjust to this change.

Some screens within SAP could be empty containers for dynamically added content (Thiscontent may be a screen or a field depending on the programmer needs). These screens arevisible in SAP Test Acceleration and Optimization, but SAP Test Acceleration andOptimization cannot create test components out of them by design.



3 Connections

28 <August 2008>

4.2.3 Performance during Test ExecutionThere is a major performance issue during the execution of the test script. If you are usingSAP Quality Center as a central repository on the network there is a performance issue whichwill cause the execution to become slower than if we were executing the process manually.

Performance issues are most of the time related to network configuration and the number oftimes that the network is being accessed. Some useful tips to make performance better are:

Make sure to use the initialize script (preconfigured test component) in every newtest

Turn the debug log off (if the test is already ready for execution) Change “application area” waiting time from 60 to 15 seconds (in QuickTest

Professional)

4.2.4 SAP Test Acceleration and Optimization/UIScanner not capturing Grid Tables

SAP Test Acceleration and Optimization / UI Scanner is not capturing the grid table and otherobjects on the standard SAP screens.

The UI Scanner approach is designed to capture up to 80% of the objects in an SAP system.It is by design that grids, trees and similar objects are not supported for scanning. Grids andtables are highly dynamic objects that can be customized and adapted for each userinteracting with that screen.

Grids and trees are not supported on either approach UI Scanner or Introspection.

4.2.5 How to Create own Components using SAP TestAcceleration and OptimizationThe SAP Test Acceleration and Optimization framework is meant to provide clients thecapability to expand its use outside of the components provided during implementation. Oneof the documents provided with the SAP Test Acceleration and Optimization install is the SAPTest Acceleration and Optimization RTL Documentation. This guide includes a list of thefunctions that are available with the framework as well as best practices around the creationof new functions and functionality within the framework.

Any change that needs to be done as a customer modification has to be done in the“CBASE_Custom_Wrappers.vbs” file; this file should be the only one containing customizedclient functions. This will allow SAP to provide better support and keep a standard framework.

If some functionality that already exists on the framework were to be modified then theoriginal function should be copied into the CBASE_Custom_Wrappers.vbs file and modifiedhere.

Standard Wrapper layout example:

Sub SAP_Wrapper_Name(FieldName, FieldValue, ReportingName)

SAP_Wrapper_Name_Location FieldName, 1, FieldValue,

ReportingName

End sub



3 Connections

<August 2008> 29

Sub SAP_Wrapper_Name_Location(FieldName, FieldIndex, FieldValue,ReportingName)

On error Resume Next

Dim OBJSET Obj = SAP_GetObject(FieldName, FieldIndex,“FIELDTYPE”,”SET/GET”)

OBJ.Method FieldValue

ReportLog “INFO”, “Step Description”, ReportingName & “ = “ &FieldValue

CheckErrorHandler()

End sub

4.2.6 SAP GUI Window Change Size on ExecutionThe SAP Test Acceleration and Optimization framework includes resizing functionality thatwill re-size the screen to allow the user to view QuickTest Professional, SAP and any otherwindow while in execution, some customer find this design uncomfortable. To remove thisbehavior, add the following code to the CBASE_Custom_Wrappers.vbs file:

sub ResetAppPosition(App)

End Sub

4.2.7 Overwrite Prompt in BCIEA feature of SAP Test Acceleration and Optimization is the ability to overwrite componentseach time one is uploaded. In order to change this functionality, change the setting underConfiguration -> Import/Export -> Overwrite Components

Mark the check box if you want the tool to overwrite the uploaded component and if you wanta serial number to be added in case you don’t want it to be overwritten leave it OFF.

4.2.8 Record Number

When you want to save a number that comes from the status bar SAP Test Acceleration andOptimization will need to know which document you are looking for. QuickTest Professionalidentifies the texts in the status bar as item1, item2 . The relevant information will be storedmost of the times in item2 and there are keywords that help SAP Test Acceleration andOptimization identify what you are looking for. A list of keywords is:

For item1:



3 Connections

30 <August 2008>

BILLING_DOCUMENT, CUSTOMER_NUMBER, TO_NUMBER, GROUP_NUMBER,DOCNUMBER, CANCELLED_DOCUMENT_NUMBER, DOCUMENT_NUMBER,PRNUMBER

For item2:

CUSTOMER_CREATED_FOR_COMPANY_CODE,PURCHASE_ORDER_NUMBER, MATERIAL_DOCUMENT_NUMBER,PURCHASE_ORDER_NUMBER, PURCHASE_REQUISITION_NUMBER,VALUE_CONTRACT_NUMBER, RFQ_NUMBER, INBOUND_DELIVERY,OEMSALESNUMBER, OMSHARDWARESALESNUMBER, MATLRELVALUECONT,STANDARDORDERNUMBER, PROMOTIONORDERNUMBER,QUOTATIONNUMBER, PROMOTIONNUMBER, ITEMPROPOSALNUMBER,SALES_ORDER_NUMBER, SALESDEALNUMBER, QUOTATION_NUMBER,INQUIRYNUMBER, INQUIRY_NUMBER

If a word that is not listed here is used then by default the item2 will be used to capture thevalue.

In order to extend the keyword functionality, please copy/paste the function Get_Status_Item from “CBASE_SAP_47_Wrappers.vbs” to “CBASE_Custom_Wrappers.vbs” and make thenecessary changes.

4.2.9 Character Removal from Test Plan NameDuring consolidation some characters are removed from test plan name to be consistent withthe SAP Quality Center functionality. SAP Quality Center test plan naming conventions andcomponent naming convention prevent some characters from being used either on thecomponent name or the parameters name. Having this in mind some characters are removedfrom component names:

4.2.10 Creating GET ComponentsSAP Test Accelerationand Optimization 1.0.10presents a new featurethat allows the creationof components to getdata from the screen.To enable thisfunctionality go to the

configuration link and tothe inspect tab:

) ! Ä @

# $ Ä %

^ & Ö *

+ = ß [

] \ Ö /

{ } Ü &| ; ü '

: " spaces ,



3 Connections

<August 2008> 31

The component type check boxes will determine the type of components that will be create,there should always be one selected. Regardless of the component type selected all theother settings will determine the behavior of the application.

Get components will provide the ability to save any value of the supported objects by storingit to a data table field (DT_), this means that all the parameters in a get component will beDT_ values.

Then you can either use these values to make a comparison or to input that into another field.

Naming convention on get components is the same as set components but with a postfix of _GET at the end of the name.

4.2.11 SAP Quality Center Required SettingsSAP Test Acceleration and Optimization 1.0.10 needs one site admin setting in the SAPQuality Center server, the parameter name needed is DISABLE_EXTENDED_STORAGE.More documentation on this parameter and how to add this to the server can be found in theSAP Quality Center admin’s guide.

4.2.12 Setup OptionsSAP Test Acceleration and Optimization installation package requires that the computerwhere it will be installed has a valid SAP Quality Center connection before SAP TestAcceleration and Optimization allows it to be installed. TAO also required the computer whereit will be installed to have a valid SAP GUI Installation.



3 Connections

32 <August 2008>

In some cases you may want to avoid those verifications, the way to achieve this is to open acommand line prompt and call the SAP Test Acceleration and Optimization setup file with thefollowing parameter:

C:\TAO Install\>setup.exe NOREQ=TRUE

Note the blank space between setup.exe and NOREQ=TRUE

This will install SAP Test Acceleration and Optimization, but please keep in mind that a validoperation without the SAP Quality Center OTA API is not possible.

4.2.13 Consolidator NotesSAP Test Acceleration and Optimization consolidation works directly with the SAP QualityCenter OTA API and this enables to work at a back end level. When working withconsolidation features here is a list of actions to keep in mind:

Save the BP before consolidating If a component will be overwritten with your consolidation:

Try to make sure that the component is not locked byanother user or yourself. This means deselect the

component from the business component module If the component being overwritten is being used by a test

make sure that you select another test on the Test Planmodule.

The 2 items mentioned above could damage the consolidation process and then areconsolidation will need to occur in order to fix the issues.

4.2.14 After-Installation NotesThe following steps are needed while working with the SAP Quality Center OTA API.Especially if you are working with different versions of SAP Quality Center (and every versionmight have a different SAP Quality Center OTA API version, too) these steps are quite useful.

Once SAP Test Acceleration and Optimization is installed in a computer the first steps to

make the environment work properly:1. Close all Internet Explorer browsers

(because the SAP Quality Center QTA API is attached to an IE Session)2. Make sure QuickTest Professional is not open3. Make sure SAP Test Acceleration and Optimization is closed4. Close all SAP Quality Center connections made from this computer

5. Connect to the SAP Quality Center server that SAP Test Acceleration andOptimization will be interacting with via Internet Explorer. This will download the SAP QualityCenter OTA API file from the SAP Quality Center server to your workstation.

This will enable SAP Test Acceleration and Optimization to work with that specific version ofSAP Quality Center.

Don’t forget to change/check the SAP Quality Center version in SAP Test Acceleration and

Optimization connect module.

4.2.15 Changing the Log File PathSAP Test Acceleration and Optimization provides the capability of changing the log file pathand also the log file name. In order to do this:



3 Connections

<August 2008> 33

1. Select the configuration link on the top right of SAP Test Acceleration andOptimization:

2. Select the Log tab:

3. In the log location section you can specify the path and name of the SAP TestAcceleration and Optimization log.

4.2.16 Component Folder inside SAP Quality CenterSAP Test Acceleration and Optimization is creating a component folder inside SAP QualityCenter. This is a known issue that occurs within SAP Test Acceleration and Optimization incombination with the SAP Quality Center OTA API when there are 2 folders called“Components” on the file system path of a component that is being uploaded.

Example:

“C:\SAPTAORTL\Components\Components \SAP R3\Common Functions\Actions\Launch_and_Login ”

This will create a component folder in SAP Quality Center behind the components root folder.

Workaround:



3 Connections

34 <August 2008>

“C:\SAPTAORTL\AnotherName\Components \SAP R3\Common Functions\Actions\Launch_and_Login ”

This will not create a new component folder and will use the component root folder as areference.

4.3 Working with QuickTest Professional (Hints andFAQ)

4.3.1 QuickTest Professional Required PatchesQuickTest Professional version 9.0, 9.1 and 9.2 will require the following patches:

QTP92P1713.exe

This fix will revert back the spy functionality to the default one, allowing inspection to work on

popups.

QTPSAP82P8116.exe

This patch is only required if working with SAP GUI 7.1

Both patches are available at your local HP support representative. Please check at local HPsupport for further patches.

4.3.2 Creating an Application Area in QuickTest

ProfessionalSAP Test Acceleration and Optimization components require an application area thatcontains the QuickTest Professional SAP add-in and the web add-in.To create this“application area” follow the next steps:

1. Open QuickTest Professional2. connect to the SAP Quality Center project through QuickTest Professional3. Select New -> Application Area4. Make sure that the SAP and Web add-ins are selected5. Save the Application Area with the name “_SAP_Doc”

This procedure will enable all the components created by SAP Test Acceleration andOptimization to execute and work properly.



5 Typical Use Cases

<August 2008> 35

5 Typical Use Cases

5.1 Inspection5.1.1 About InspectionInspection is the most powerful feature in SAP Test Acceleration and Optimization. Useinspection to:

Select transactions from a list of current transactionsAdd new transactions to the current transaction listSend the transactions to SAP Quality Center server and/or a designated directory

One Business ProcessWhen planning a business process test, consider that SAP Test Acceleration andOptimization can generate one business process test at a time. If a business process loops,

has inputs or branching logic, or deviates from the logic of the first iteration, split the processinto multiple tests. Ultimately, each business process translates into one test script.When you specify a business process, specify as much static data as possible within thebusiness process definition.You can always define dynamic or consumable data in a separate process.

5.1.2 Using Inspection to Select TransactionsOpen the Inspection screen from the SAP Test Acceleration and Optimization navigation bar.Inspection allows you to import transactions for your business process test. The Transaction List is unpopulated when you first install SAP Test Acceleration and Optimization.Use the Add to List and Remove from List buttons to populate and modify the list as needed.

5.1.3 Add a TransactionSAP Test Acceleration and Optimization allows you to add one transaction code at a time.

To add a transaction code1. Click Add . The Add Transaction pop-up window opens.2. Enter a transaction code.3. Enter a description for this code in the Description field. (Optional)4. Select an Importance level from the pull-down list (Business Critical, Warning, Information,Ignore).5. Click Add. The Transaction Code appears in the Transaction List.6. Repeat these steps for each transaction code you want to add.

To add the most used transaction codes automatically

If you want to add the most used transactions (remark: this will need the statistics in the SAPback end system configured correctely) automatically by SAP Test Acceleration andOptimization, simply select the function “Get weighed list of most used transactions”. Thisfunction will fill the list of transactions accordingly.



5 Typical Use Cases

36 <August 2008>

5.1.4 Remove a TransactionSAP Test Acceleration and Optimization permits you to remove one transaction at a time.

Important: if you wounld like to remove a transaction, please ensure that NO screens areselected for this transaction in the right part of the window. You will not be able to navigate tothere unless you add the same transaction code again.

To remove a transaction1. Select the transaction code you want to delete.2. Click the left column. The Remove icon (an X inside a circle) appears.3. A confirmation dialog appears to remove the specific transaction code.4. Click Yes . The transaction code is removed from the list.

5.1.5 Perform InspectionThe inspection screen displays a group of transactions and associated screens. You mayselect one or more SAP transaction code combinations as required by your businessprocesses. Inspection determines if the transactions are valid, and sends them to SAPQuality Center. A valid transaction contains screen objects that connect to metadata, or data

stored in tables.

To perform inspection1. To select one or more screens associated with a transaction code, select the Transaction Code in the Transaction List. The screen associated with this transaction code opens in theTransaction List .

2. To select all the screens, click the Check All link at the bottom of the screen.



5 Typical Use Cases

<August 2008> 37

3. To choose specific screens, select the checkbox beside each screen.

4. Repeat steps 1–3 to add additional transactions.

5. To view a list of the transaction codes and screens you have selected, click the View All link in the Run Inspection box. You can print out this list.

6. To remove a screen, go back and select each transaction code that you want to changeand deselect the box.

7. Click Inspect . Scroll to the right in the Results Window and review the three columns:Inspection Result , CompCreatorResult (the directory you specified to save inspectionresults), and the Upgrade Result . All three columns must contain an “OK ” for the screen tosuccessfully upload to SAP Quality Center.

8. If one or more screens fail Inspection , reinspect any screens that failed. If these screenscontinue to fail:a. Use the UI Scanner to capture the screen.b. Send the screen to SAP Quality Center.

NoteSAP Test Acceleration and Optimization may not recognize screen objects that aredynamically generated in code or are tagged as (empty container screens).



5 Typical Use Cases

38 <August 2008>

5.1.6 Using the UI ScannerThe UI Scanner is an add-on for QuickTest Professional. It scans most of the data in thescreen and is less restrictive than inspection.

The UI Scanner is able to detect the open SAP GUI sessions and will show them in the SAP

Test Acceleration and Optimization UI.

To run UI Scanner1. Minimize all the windows on your computer except the screen that you want to scan, SAPTest Acceleration and Optimization and QuickTest Professional.

2. Navigate to SAP Test Acceleration and Optimization inspection -> UI Scanner

3. Click Launch UI Scanner . The UI Scanner opens the captured transaction code inQuickTest Professional.

4. Wait for the “Done ” message.

5. Name and Save the transaction code window. The UI Scanner sends the screen to SAPQuality Center.

6. Open the newly scanned transaction code in SAP Quality Center and add it to an existingor a new script.



5 Typical Use Cases

<August 2008> 39

5.2 Building Test Scripts in SAP Quality CenterNote:The following explanations briefly outline the typical use case, but are not able to replacedeep SAP Quality Center knowledge

Building your SAP application test scripts requires the SAP Quality Center, an application thatprovides many test management functions.

At this point, you have verified that your business processes work and have split them intological components. SAP Test Acceleration and Optimization components should not containflow logic or operations that span multiple SAP screens or views. An ideal componentcontains a small number of operations and can function independently. An example of a SAPTest Acceleration and Optimization component is entering an activity. The componentdefinition only contains the steps required to complete the form or applet. It does not includeapplication logic, such as clicking on the New or OK button. You can add these buttons asseparate components during the script building process.

Some operations are always performed together; therefore it is makes sense to group thesetogether in a component. For example, whenever a user clicks a Query button, the next step

requires the user to perform the query, followed by clicking GO .This section describes only SAP Quality Center buttons and actions that you use to build testscripts. Use the Test Plan section in Business Components to build a test script. Refer to theSAP Quality Center documentation for information about other functionality.

5.2.1 Logging onto SAP Quality CenterYou must be an SAP Quality Center project administrator to use SAP Quality Center (alsoreferred to as HP Quality Center).

To log on to SAP Quality Center1. On the upper right corner of the SAP Test Acceleration and Optimization client, click theSAP Quality Center link to open the respective homepage.

2. Click HP Quality Center on the HP Quality Center server homepage.

3. On HP Quality Center homepage, enter your user ID and password.

4. Click Authenticate . If you checked “Automatically log in to my last domain and project on this machine,” HP Quality Center automatically completes the fields with your domain andproject and logs you in.

5.2.2 Building a Test ScriptUse the Test Plan module in SAP Quality Center to build a test script.

To build a test script1. Navigate from Business Components to Test Plan in SAP Quality Center.

2. Click Test Plan .

3. To create a new folder:a. Click Tests .b. Select New Folder .c. Enter a name for the folder.



5 Typical Use Cases

40 <August 2008>

d. Click OK .

4. To create a new test:a. Select the folder where you want to save the test.b. Select New Test. A pop-up dialog box opens.c. Select Business Process from the pull-down test type.

d. Enter a name for the Test.e. Click OK . The Details tab displays your name, the test name, the creation date, and thestatus.

5. Click the Test Script tab to build your script. A components tree opens in the right column.Navigate to the location on the components tree where your transactions are stored.

6. Navigate to the SAP actions and buttons. Open the Actions folder and navigate to Initialize Script. Make the first component in the test plan Initialize Script if you plan to parameterizethe values in this script. Initialize Script adds a link in the test script title to the Excelspreadsheet. See the next section, Parameterizing the Elements in the Test Script , for moreinformation.

7. Use drag and drop commands, buttons, and transactions as needed to create the test.

8. Save the test. Use the small disk icon.After you build the script, verify that you have added all the necessary elements in a logicalorder. Once you have verified the elements, you may parameterize elements or proceed tothe next chapter to consolidate the test script.

5.2.3 Parameterizing the ElementsParametrization allows a business component to receive data from an external source, or toreturn data for use in other components. You can store the parameterized elements in anExcel spreadsheet or in the SAP Quality Center database.SAP Test Acceleration and Optimization provides an Excel spreadsheet mechanism to storeparameters. The initialization script that you create in the SAP Quality Center server Test

Plan specifies the name of the associated spreadsheet.

All parameters that you intend to store in the Excel spreadsheet must use the DT_ prefix. TheDT_prefix parameters are useful for storing and creating variables that change fromexecution to execution.For example, a payroll application may include a current date that changes from week toweek. By storing the parameter in an Excel spreadsheet, you can create a function to updateit. SAP Test Acceleration and Optimization reads the new value from the spreadsheet eachtime you re-execute this script.

If you parameterize a value, but do not include the DT_ prefix, the value becomes static orhard-coded. Designate a value as hard-coded when it stays the same from one execution tothe next. When you hard code a value into a parameter, the SAP Quality Center serverinserts this exact value each time it encounters this parameter in a test script.

To create a SAP Test Acceleration and Optimization parameter entry1. Open the test script that you want to parameterize.

2. Click the data value that you want to parameterize. The Components Iteration windowopens.

3. Enter the value and include the DT_ prefix to the data value name.



5 Typical Use Cases

<August 2008> 41

4. Specify whether this value is output for use in another component, or whether you want tosave it for reuse.

5. (Optional) You may enter an description for this value.

6. Click OK .

Follow these six steps to parameterize as many values as required.

To create a hard-coded parameter entry1. Open the test script.

2. Click the data value that you want to parameterize. The Components Iteration windowopens.

3. Enter the value.

4. Specify if this value is output for use in another component or whether you want to save it .

5. (Optional) You may enter an description for this value.

6. Click OK .

5.3 Consolidating Test Scripts in SAP Quality CenterConsolidating creates one component from the elements in your test script. The newcomponent contains all the code and screen elements from the test script.

5.3.1 Consolidating Test PlansWhen you save a test script in the SAP Quality Center, the components are saved in adesignated folder in the SAP Test Acceleration and Optimization system.

To consolidate in the SAP Test Acceleration and Optimization client1. Make sure to save the test script in the SAP Quality Center.

2. Open the SAP Test Acceleration and Optimization client and click Consolidate .

3. Choose the Select a Test Plan tab.

4. Navigate to the folder where you saved your test script.

5. Select the test script you want to consolidate and click Consolidate .

6. A message at the bottom of the screen details the Consolidation progress.



5 Typical Use Cases

42 <August 2008>

5.3.2 Consolidating Selected ComponentsUse this screen when you update a component and need to propagate the update to multiplebusiness processes.

Consolidate by components:

This feature enables you to consolidate all or some of the tests that use a given component.This provides the ability to consolidate several business processes from a list that isgenerated after a component is selected. (The list represents all the business processesusing the selected components.)

Example:

If Component 1 is modified and it is used in 10 business processes, using this feature willenable the user to select Component 1 from the list of components (left hand side of thescreen) and the business process list will be populated by all 10 tests that use thiscomponent. The user is now able to select which of these tests he wants to reconsolidatewith the check boxes to the left of each business process. When the user clicks theConsolidate button all the selected tests will be consolidated.

To consolidate selected components:1. On the Consolidate page, click the Select by Component tab.

2. In the tree view, navigate to the test component you want to consolidate.

3. Click the test component. The business processes that use this component appear in atable below the test component.



5 Typical Use Cases

<August 2008> 43

4. Select the business processes you want to update with the new information. Deselect abusiness process if you do not want to reconsolidate it.

5. Click Consolidate .

5.4 Importing and Exporting ComponentsThe Import and Export module primarily works in the background any time you transfercomponents between the SAP Test Acceleration and Optimization client and SAP QualityCenter server. The user interface is useful for manual maintenance activities. You may wantto transfer components to:

Back up components on the SAP Quality Center server or on a hard drive.Transport components from one SAP Quality Center server project to another, or from one

server to anotherDownload components f rom SAP Quality Center.

There is no limit to the number of components you can import or export.

5.4.1 Exporting Test ComponentsWhen you export a component from SAP Test Acceleration and Optimization to the SAPQuality Center, the component gets stored in the file that you designated in Connections.

To export components from the SAP Test Acceleration and Optimization1. In the SAP Test Acceleration Optimization navigation bar, click Import/Export .

2. Navigate to the directory in the SAP Test Acceleration Optimization directory.



5 Typical Use Cases

44 <August 2008>

3. Select the checkbox next to the transactions that you want to export to SAP QualityCenter.

4. Click Export to SAP QC . The status bar indicates the export’s progress.

5. Check the designated folder on the SAP Quality Center to make sure the Exportsucceeded.

5.4.2. Importing Test ComponentsWhen you import a component from the SAP Quality Center, you can store the component inany location for which you have persmission.

To import components from the SAP Quality Center1. In the SAP Test Acceleration and Optimization navigation bar, click Import/Export .

2. Navigate to the directory you want to import from on the SAP Quality Center.

3. Click the box next to each of the components you want to transfer.

4. Click Import From SAP QC .

5. A Browse For Folder popup opens. Browse to the folder where you want to store thecomponents.

6. If you need to make a new folder:



5 Typical Use Cases

<August 2008> 45

a. In the Browse Window, browse to the folder or directory where you want to make a newfolder.b. Click Make New Folder . A new unnamed folder appears in the directory.c. Enter a name for the new folder

7. Click OK .

8. Make sure that the new folder exists and that it contains the exported components.