User Guide

SAP® Test Acceleration and Optimization 1.0.10
Target Audience Quality administrators Application testers

Document version: 1.0 – August 7, 2008

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

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

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

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

You can find this documentation at the following address:
http://service.sap.com/instguides

(hereinafter: Customer)

Terms for Included Open Source Software
This 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 and conditions 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

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 or any 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.

Permission to use, copy, modify, distribute and 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 no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. 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. 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 the STLport. 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. the Adobe logo. Adobe Document Services Adobe.000. 4 if this loss could have been avoided by observing this obligation. Acrobat. SAP shall not be liable for the loss of data and its recovery. in particular by making backup copies at the minimum intervals recommended by SAP. PostScript. 4 includes claims against employees or agents of SAP. 4. see SAP Note 854621. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer. E) The Customer shall take adequate measures for the protection of data and programs. F) The exclusion or the limitation of claims in accordance with the present Art. . notwithstanding the other limitations of the present Art. and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries.

and key concepts of a programming language when they are surrounded by body text. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. for example. transaction codes. Cross-references to other documentation Example text Emphasized words or phrases in body text. names of variables and parameters. This includes file and directory names and their paths.Typographic Conventions Type Style Example Text Description Words or characters quoted from the screen. and menu options. For more information. SELECT and INCLUDE. menu paths. program names. F2 or ENTER. These are words or characters that you enter in the system exactly as they appear in the documentation. Icons Icon Meaning Caution Example Note Recommendation Syntax EXAMPLE TEXT Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. source text. These include report names. These include field names. Exact user entry. and table titles Technical names of system objects. screen titles. Output on the screen. Keys on the keyboard. graphic titles. Variable user entry. table names. and names of installation. for example. messages. see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library. Example text Example text <Example text> EXAMPLE TEXT . pushbuttons labels. upgrade and database tools. menu names.

.................................................... 25 4............................... 29 4.................... 16 2..3 Licensing SAP Test Acceleration and Optimization ....................................................2........... 28 4.................10 Creating GET Components........................2............2 Installing SAP Test Acceleration and Optimization Runtime Library (RTL) Parts .......................... 25 4..................................................................2.....2 SAP Test Acceleration and Optimization Inspection ....8 Record Number ........................................................ 25 4.........................................................5 Logging Options..........1....................................................................................................................................................................1 Installing SAP Test Acceleration and Optimization Client ............................Contents 1 Introduction ...............9 Character Removal from Test Plan Name ..............................1 About this Document ...................................................2..........3 Import/Export Options .......................................11 SAP Quality Center Required Settings....... 9 1............2.......................... 29 4...........2 Connecting the SAP Quality Center Server ................3 Performance during Test Execution.........23 3........ 12 1.................................................1.....................1.....................................................................1 Configuration of SAP Test Acceleration and Optimization ...............12 Setup Options ...................................................4 SAP Test Acceleration and Optimization/UI Scanner not capturing Grid Tables ...9 1..........1................................... 31 4.............................. 27 4...................................... 28 4......................................................2............ 27 4.......... 20 2.................................................4 Settings in SAP Quality Center ... 29 4............................................1 Usage of SAP Quality Center/QuickTest Professional Output Parameters ................ 30 4.........2.............................4 Consolidate Options ............................................ 13 2 Installation ...2............................................. 25 4.......................... 28 4...............1 SAP Notes for the Installation ................. 23 4 Additional Information...............................1.......14 2.......2...... 31 <August 2008> 7 .................................. 27 4....25 4.......2 Inspection Options.... 27 4. 23 3...6 Expert Settings ........2 Before You Start ........................................2..6 SAP GUI Window Change Size on Execution ...................................................................2.................................2.....7 Overwrite Prompt in BCIE........... 21 3 Connections ........................... 12 1.......2 Working with SAP Test Acceleration and Optimization (Hints and FAQ) ................1.....................................................1 Connecting the SAP Server......................2 Information Available in SAP Service Marketplace ......................1 Self Test ........ 19 2.......... 26 4...2............................................................................... 26 4.....5 How to Create own Components using SAP Test Acceleration and Optimization ....2...... 30 4.........................................

....................15 Changing the Log File Path ........................ 32 4....................2.......................................14 After-Installation Notes.................. 35 5................ 43 5...............1 Consolidating Test Plans....... 35 5................. 35 5...............................1 Inspection ....................................................................................................2 Creating an Application Area in QuickTest Professional ...3 Add a Transaction ................2...................2.1..........16 Component Folder inside SAP Quality Center ............ 34 4...................3... 39 5.............................. 41 5.... 36 5.3 Working with QuickTest Professional (Hints and FAQ) .....................1....................... 32 4............. 36 5..2.....4.1.................. 43 5............................. Importing Test Components..................2 Consolidating Selected Components.................................................................2.................... 41 5...........3 Parameterizing the Elements ...............3....... 35 5..........4 Importing and Exporting Components.............................................4 Remove a Transaction .1............3 Consolidating Test Scripts in SAP Quality Center ............................................... 34 4................................4........2.6 Using the UI Scanner ....................................... 39 5........2.1 About Inspection ........................ 42 5.................1 Exporting Test Components ..............3..Installation Guide: SAP Test Acceleration and Optimization 4.................... 39 5.............................1...........2 Building a Test Script .....................1................1 Logging onto SAP Quality Center................. 33 4........................................................................................................................................5 Perform Inspection..................... 44 8 <August 2008> .3...................... 40 5.............2 Using Inspection to Select Transactions ............... 32 4...2 Building Test Scripts in SAP Quality Center...........................35 5...........................13 Consolidator Notes ............... 34 5 Typical Use Cases ....................................................................1 QuickTest Professional Required Patches ...............................2............. 38 5..

or service packs change.1 About this Document Purpose The highly secure and mission-critical nature of enterprise resource planning (ERP) data means that customers need to regularly test ERP applications and business processes. You can also move components from SAP Quality Center to SAP Test Acceleration and Optimization for additional backup possibilities. Inspection examines the data content within a component. Automated testing with SAP Test Acceleration and Optimization maximizes: Testing Deployment SAP Test Acceleration and Optimization. dramatically reduces the amount of time required to build and execute test scripts. Robustness The SAP Test Acceleration and Optimization inspection process ensures that SAP Test Acceleration and Optimization tests are more robust during changes. not just the screen object behavior. Many SAP customers use customized manual procedures to test processes and applications at great expense to the company. SAP GUI ERP applications. The SAP Test Acceleration and Optimization (SAP TAO) application streamlines the creation and maintenance of ERP business process testing. SAP Test Acceleration and Optimization users should be experienced quality administrators who are familiar with the SAP Quality Center application by HP (also referred to as HP Quality Center). Reuse SAP Test Acceleration and Optimization eliminates the need to create new tests whenever a component changes. just replace that component and then re-consolidate the tests. in tandem with SAP Quality Center. <August 2008> 9 . subject matter experts often devote extra hours communicating the process data flow to the testers. such as reusing a test that has updated data inputs Maintained easily and inexpensively. flows. even when screens. SAP Test Acceleration and Optimization provides a Microsoft Excel spreadsheet to save parameters for reuse and maintenance. Manual testing is time-consuming and frequently requires a team of experienced quality assurance (QA) professionals. and business process testing. In addition. SAP Test Acceleration and Optimization helps QA specialists to break down an application into components which are: Assembled into test cases through a simple interface using drag and drop Parameterized for flexible reuse. If one component changes in a group of tests. 1. SAP Test Acceleration and Optimization is designed for SAP-GUI-based applications.1 Introduction 1 Introduction This guide describes the installation and first steps in the usage of SAP Test Acceleration and Optimization (SAP TAO). Maintenance SAP Test Acceleration and Optimization allows you to record component parameters.

If you reconsolidate this component. 10 <August 2008> . The UI Scanner scans all objects in the screen including dynamically generated objects. It enables you to create and maintain a list of transactions and screens and to add and delete transactions from this list. but executes much faster than the individual components. Inspection Inspection captures the data in a screen or transaction and determines its validity. such as moving components from server to server or from project to projects. enables you to collect information from one screen at a time. reconsolidate. The UI Scanner need a running QickTest Professional (QTP) installation on your local workstation. Functional Blocks The SAP Test Acceleration and Optimization client application runs on a Windows system. and consolidating components or scripts from SAP Quality Center. changes. change the parameter in the component. exporting the transactions to SAP Quality Center. o The UI Scanner. Import/Export Import/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. It then determines whether these screens and transactions are valid and sends the valid screens to SAP Quality Center. and sends the screen objects to SAP Quality Center as a component. It performs three key functions: Inspecting transactions from a SAP server. The Import/Export module performs the following functions: Exports components from the Inspector in the SAP Test Acceleration and Optimization client to SAP Quality Center Imports components from SAP Quality Center to the SAP Test Acceleration and Optimization client Exports a component from the UI Scanner and sends it to SAP Quality Center in background mode Consolidation Consolidate gathers all the objects and data in an SAP Quality Center test script and creates a single component. To update one parameter in a process. The SAP Test Acceleration and Optimization application provides two modes of inspection: o The Inspect screen in the SAP Test Acceleration and Optimization client enables you to select multiple SAP GUI screens and transactions for testing in an easy to use interface.1 Introduction Integration The SAP Test Acceleration and Optimization application requires products from SAP and the SAP Quality Center. you have a component that contains all the code in the test script and other components. and reexecute the component. it is also helpful for maintenance functions. These “super components” help you maintain business processes.

which the Inspector leverages against SAP Quality Center components. use the Inspector to specify the transactions that you need to create a test script. and a properly installed and connected SAP Test Acceleration and Optimization client on your desktop. 4. It enables both non-professionals and QA experts to streamline testing SAP applications and business processes. Discuss the process flow with the subject matter expert. 3. Enter. with the SAP R/3 server and SAP Test Acceleration and Optimization. SAP Quality Center The SAP Test Acceleration and Optimization application uses the following components from SAP Quality Center: o SAP Quality Center SAP Quality Center is a complete system for automated and manual testing. SAP Quality Center includes a list of common screen commands. Run the steps manually within the test application to make sure the application generates without errors or warning messages. SAP Test Acceleration and Optimization leverages QuickTest Professional recording features with the UI Scanner. b. and Exit. It captures. Together. Add other transactions as needed.1 Introduction Technical Components SAP Server The SAP R/3 or ERP (version 46c or later) server stores screens and transaction metadata. Parameterize the data in the SAP Test Acceleration and Optimization Excel spreadsheet or the SAP Quality Center database. a. Typical Use case This section describes how to test a simple business process with SAP Test Acceleration and Optimization and SAP Quality Center. “Installation”. o QuickTest Professional QuickTest Professional is an automated test solution for functional and business process applications. it creates a complete automated testing environment. For greater detail on installing and connecting SAP Test Acceleration and Optimization see Chapter 2 . 6. It reduces test maintenance and simplifies test creation with drag and drop functionality. Move the screen commands using drag and drop as needed. such as Open. Create a business process test case with detailed steps. <August 2008> 11 . Open SAP Quality Center to view the list of your selected components. “Connections. In the SAP Test Acceleration and Optimization client. 2. 5. and Chapter 3 . verifies.” 1. access to SAP Quality Center. Drag and drop the transactions in the order that they occur in the business process. QuickTest Professional is also required t o execute testing scripts in SAP Quality Center. It assumes that you can access a SAP back end server that executes the business process transactions you are testing. and replays user interactions automatically.

2. many UI techniques can be scanned and evaluated. 8. 9. SAP Note Number 1231935 Title Installation SAP Test Acceleration and Optimization 1.10 Description Installation note 12 <August 2008> . you can capture UI/screen elements but it depends on the real usecase if this capturing can be used to transform it to a test component. Make sure that you have the up-to-date version of each SAP Note.2 Before You Start The following sections provide information about: SAP Notes for the installation Information available on SAP Service Marketplace Naming conventions 1. On SAP Test Acceleration and Optimization. Execute the test script and review it for any discrepancies. consolidate the data into a single component that consists of the transaction code and screen operations. Because UI Scanner uses QuickTest Professional for screen capturing.1 SAP Notes for the Installation You must read the following SAP Notes before you start the installation. 10. Following the basic idea of QuickTest Professional. These SAP Notes contain the most recent information on the installation.0. which you can find in the SAP Service Marketplace at the Internet address: service. as well as corrections to the installation documentation. you can create SAP Test Acceleration and Optimization compatible test components as well. Save the components in a directory that you can easily access when you need to update a screen or a transaction. Constraints SAP Test Acceleration and Optimization release 1 does only provide direct support for SAP GUI based applications. 1.sap. In the SAP Quality Center. Using the build-in UI Scanner which is build on top of QuickTest Professional. create a second business process script using the single component.1 Introduction 7.com/notes.

com/platforms service.com/sizing service.sap.2.com/notes service.1 Introduction 1.sap.com/security <August 2008> 13 .2 Information Available in SAP Service Marketplace Information on the following areas is available in the SAP Service Marketplace. General Quick Links Description SAP Notes Released platforms System sizing Front-end installation Internet Address service.sap.sap.com/instguides Title – – Quick Sizer tool Front End Installation Guide – Security service.sap.

“C:\Documents and Settings###BOT_TEXT###lt;user>\Local Settings\Application Data\SAP_AG\SAPTAO.) “C:\Program Files\SAP\SAP TAO\WORK”. you have to de-install the old version using the standard Windows tools. If your back end system does not have the appropriate support package level. Please remove these files if you have any security reasons.2 Installation 2 Installation This chapter is about the installation of SAP Test Acceleration and Optimization on your local workstation. 14 <August 2008> . that the new SAP Test Acceleration and Optimization will start from a clean environment. “C:\Program Files\SAP\SAP TAO”).) SAP Test Acceleration and Optimization agent for ABAP You need the SAP_BASIS component from 46C to 7. Please get in contact with you local SAP representative.config”) is also not removed.10 having a specific support package level. General remark to the uninstalling of SAP Test Acceleration and Optimization: The Windows-based uninstalling procedure of SAP Test Acceleration and Optimization will recognize only files that were installed during the initial installation process.exe_Url_<hash>###BOT_TEXT###lt;version\user.e.e. “C:\Program Files\SAP\SAP TAO”) to something different. You need this function module in every back end system that you want to work with. Prerequisites for installation As prerequisites you need: 1.e. 2.e. Before you can install the new version. These files might 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. Example: SAP_BASIS 700 needs a SP level of 12. This folder will not be deleted by the de-installer but will contain technical files that were created using the old SAP Test Acceleration and Optimization version. The user specific configuration file (i. The uninstallating process will not remove any files in the “. You can simply check for existence of the function module “TMW_TAOAGENT” in your back end systems to determine the correct support package level. The recommendation is to de-install the old version and then to rename the application folder (i.) SAP GUI You need a valid and running SAP GUI installation of you local workstation. Patching from an older version of SAP Test Acceleration and Optimization The following steps are equal for patching an existing SAP Test Acceleration and Optimization version of you local workstation to the new version.\WORK” folder. it might be possible to install the function module as a customer extension. Please archive or save the working folders under (i.

) QuickTest Professional You need to have QickTest Professional (9. 9.2. Distribute the SAP Test Acceleration and Optimization Runtime Library (RTL) on each computer that is configured to execute tests.5) installed on your local workstation. The SAP Test Acceleration and Optimization installer checks to see if the SAP Quality Center API has been installed.5) And from Quality Center add-ins page: * QuickTest Professional add-in * QuickTest Professional for Business Process Testing add-in Procedure The following list provides the steps and installation requirements to set up SAP Test Acceleration and Optimization.) SAP Quality Center You need a running SAP Quality Center instance in your landscape (release 9. The SAP TAO RTL is installed during the main installtion of SAP Test Acceleration and Optimization. 5.0. 2. 3. <August 2008> 15 . 9. install QuickTest Professional and the requisite add-ins on each computer that will run SAP Test Acceleration and Optimization. 4. Install the SAP Quality Center API on each computer that will run SAP Test Acceleration and Optimization. The installation of the SAP Quality Center API is performed by connecting and logging in to an SAP Quality Center server. If this is not possible for any reason please get in contact with you local SAP representative to find a solution for licensing SAP Test Acceleration and Optimization. * Quality Center Connectivity add-in * Quality Center Test Remote Agent add-in 5.) SAP Solution Manager SAP Test Acceleration and Optimization needs a connection to a SAP Solution Manager instance (as of SP17) for licensing purposes. 4. If your SAP Solution Manager is not SP17 it is highly recommended that you update your SAP Solution Manager to SP17 or higher. Check the SAP Test Acceleration and Optimization RTL init file (“CBASE_init_vbs”) and add parameters on SAP Quality Center.0.1.2 Installation 3.2) having the Business Process Testing module installed. 1. If you plan to execute tests or run the UI Scanner. 9. In addition you need to ensure that the following QickTest Professional add-ins are installed: * QuickTest Professional SAP GUI add-in (included in QuickTest Professional 9. 9. Verify the availablility of the SAP Test Acceleration and Optimization agent for ABAP on the SAP server or the SAP ERP system.

2. Double click on setup. The SAP Test Acceleration and Optimization installer checks to see if the SAP Quality Center is available. Click Next 3.10.2 Installation 6. Go to the Service Marketplace and download the complete installer file for the SAP Test Acceleration and Optimization client 1. 16 <August 2008> . Run the executable installer file (setup.1 Installing SAP Test Acceleration and Optimization Client The following instructions assume that you have installed all prerequisistes including the SAP GUI and SAP Quality Center Web access on this system. 2. SAP Test Acceleration and Optimization can be installed through the network like any msi file. To optain a valid license for your SAP Test Acceleration and Optimization installation you simply can configure the connectivity to an SAP Solution Manager instance in your landscape. To install the SAP Test Acceleration and Optimization client on each computer 1. the installation cover in this guide is the standard single client installation. Install the SAP Test Acceleration and Optimization on each the system in step 4.exe 2.exe) and accept all the defaults.0. SAP Test Acceleration and Optimization provides a configuration dialog to administer this connection. 7. 1.

2 Installation 4. Select the path where SAP Test Acceleration and Optimization is going to be installed 5. Click Next <August 2008> 17 .

2 Installation 6. LOGS and OBJRef folder a.1.2) 18 <August 2008> . 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 the SAP Test Acceleration and Optimization RTL CBASE. NOTE: If this is the first installation this path will be where you will later copy the CBASE folder(see step 2. Confirm your settings by clicking Next 7.

After pasting the folder rename it to CBASE (without the “_Default” string) The final folder structure should look like this (using default settings): <August 2008> 19 . Once a SAP Test Acceleration and Optimization installation is completed all the Prebuild components will be in the installation folder (i.2 Installing SAP Test Acceleration and Optimization Runtime Library (RTL) Parts The following instructions only need to be applied once for each new project (a project is determined by a SAP Quality Center project) and only after the first installation of SAP Test Acceleration and Optimization is completed: 1.e.2 Installation 8. “C:\Program Files\SAP\SAP TAO”) then “COMPONENTS_Default” a. Go to the installation folder (by default “C:\Program Files\SAP\SAP TAO”) select the folder called “CBASE_Default” and copy paste it into the path that you specified in step #6 of the Installation section. 2. 3. This folder could be local or on a central file share. This folder will be the one that needs to be imported when uploading all the components to start a project 2. The installation of SAP Test Acceleration and Optimization is complete.

In order to setup this license you will need to go into configuration. This model is now server-based where a SAP Solution Manager (having SP17 or higher) instance will now distribute licenses to the clients.0.3 Licensing SAP Test Acceleration and Optimization SAP Test Acceleration and Optimization 1. 20 <August 2008> .2 Installation 2.10 presents a different and improved licensing model.

Please see the further documentation on the parameter “DISABLE_EXTENDED_STORAGE” mentioned later in this documentation. Then click the Check for license button and finally Save.4 Settings in SAP Quality Center There are some settings to be made in the SAP Quality Center server as well. Provide the correct login information.txt”) to your SAP Quality Center.2 Installation Here you will find all the available SAP servers on your SAP logon. In addition you need to upload the file (i. Click the Test SAP connection button.vbs. Please refer to the following screen dump for a sample look-a-like: <August 2008> 21 . Now your local instance of SAP Test Acceleration and Optimization is enabled. “C:\SAPTAORTL\CBASE\CBASE_Init.e. 2.

2 Installation 22 <August 2008> .

complete the following information: a. Domain – The SAP Quality Center domain for your project. Password – The password you use to connect to SAP Quality Center. <August 2008> 23 . QuickTest Professional Version – The QuickTest Professional version number. then you must re-enter and save the new connection information. 3. User – The name you use to connect to SAP Quality Center. If you change the connection path. SAP Test Acceleration and Optimization remembers the saved connection settings the next time you log in. 3. On the SAP Logon window. To open a connection to SAP Quality Center. On the SAP Quality Center side of the window.) d. Project – The first time you connect to SAP Quality Center. Click Save.1 Connecting the SAP Server 1. Client – The SAP client number assigned to this server area. 3. or domain. click Log In. f. Use this format when you create new users or change passwords. Click the Connect icon in the SAP Test Acceleration and Optimization navigation bar. The Connection screen assumes that you can access the SAP server and the server where the SAP Quality Center resides.2 Connecting the SAP Quality Center Server The right side of the Connect screen provides SAP Quality Center server connections. d. To connect to the SAP Quality Center. SAP Quality Center creates a name for each project you begin and adds the project name to the Project pull-down list. Password – The SAP Password for this user (The RFC Communication is based on the standard compatible format of passwords: 8CHARS (non mixed). b. c. SAP Test Acceleration and Optimization supports English (EN). 2. select a server from the list. at first specify a project and domain and then save the connection. c. Language – The language you want the system to use.3 Connections 3 Connections Use the SAP Test Acceleration and Optimization Connection screen to specify connections to SAP servers and SAP Quality Center server. Click Test Connection to SAP to verify the connection. 3. Complete the following fields: a. b. g. In the SAP Test Acceleration and Optimization navigation bar. e. User ID – The SAP User ID. 5. accept the default project. SAP Quality Center Version – The SAP Quality Center server version number. Server URL – The SAP Quality Center URL. You must know the access paths and passwords for these servers. 2. click Connect . 4. the project. You must perform these steps on each SAP Test Acceleration and Optimization client. 1.

To open a designated project in SAP Quality Center. click Connect to Project. 5. Click Save. if you want to change the information. 6.3 Connections 4. SAP Test Acceleration and Optimization remembers the saved connection settings the next time you log in. 24 <August 2008> . However. enter the new data and re-click Connect to Project. Click Save.

1. click the Configuration link on the upper right corner of the SAP Test Acceleration and Optimization interface.1. 4.3 Import/Export Options Use the Import/Export settings to designate a path for transferring components from SAP Quality Center to an SAP Test Acceleration and Optimization client. The tabs in the Configuration screen are: Self test Inspect Import and Export Consolidate Log License (see 2. 4. To access this screen. Use the Component Location to specify the directory. If you select Generate Components and this setting. 4. Export from is the path where the SAP Quality Center sends components.1 Configuration of SAP Test Acceleration and Optimization Use the Configuration screen to select settings for the following SAP Test Acceleration and Optimization client functions. you can easily check for a correct installation of SAP Test Acceleration and Optimization.3) Expert Settings Please check the tool tips for a quick reference to the function. Component Location is the path to the local directory where you want to store saved components.1. Upload the Components to Quality Center moves the components to SAP Quality Center server.2 Inspection Options The following buttons designate what action the SAP Test Acceleration and Optimization client takes when you select transactions: Generate Components Locally saves components in a specified directory. Please check for further notices in the Info Box (see “Expert Settings”). <August 2008> 25 .1 Self Test Using the self test function of SAP Test Acceleration and Optimization.1.3 Connections 4 Additional Information 4. the components go to both SAP Quality Center and the specified local directory.

5 Logging Options Use the Log Options tab to set log file detail levels and to specify a directory to save files. 4. Use this prefix if you intend to save parameters in SAP Quality Center for reuse.1. Prompt for confirmation before consolidating – SAP Test Acceleration and Optimization displays a prompt to consolidate before each it consolidates components. 26 <August 2008> . a. This step ensures that you do not have components with the same name. SAP RFC Trace Level 2. Consolidate Settings Created in SAP QC Folder –The path to the folder where new components created in SAP Quality Center are stored.4 Consolidate Options This screen contains Consolidate and Data Table settings. Deselect this checkbox if you do not want to append the component name to each test script. 4. Specify a trace level for each log. SAP Test Acceleration and Optimization creates a database for each script that you build in SAP Quality Center.1. specify the path to the directory where you want to save log file. Internal Trace Level b. Enter the Data Table Parameter Prefix – The default data table Prefix is: DT_. but only recognizes parameters with the DT_ prefix.3 Connections Overwrite Components in SAP Quality Center indicates that SAP Test Acceleration and Optimization overwrites a component if it encounters a new component of the same name. but with different data. Data Table Settings Update the data table file – Select this checkbox to ensure that the data table is updated automatically. The default setting is 1 or Warning. The log levels are: 0 = None 1 = Warning 2 = Message and Stack 3 = Debug To specify a log trace levels 1. Overwrite Consolidated – SAP Test Acceleration and Optimization overwrites duplicate components with the most updated data (Default). Additional Settings Add the component name in consolidated script – SAP Test Acceleration and Optimization appends the component name to each consolidated test script (Default). (Default). In the Log Location field. SAP TAO Trace Level c.

This data may be stored in a different format or even not stored in this metadata at all.2. the inspection provides a way of automatically generating components by searching in the metadata the information of the objects contained in a given screen. In the Windows Temp text box. The SAP Test Acceleration and Optimization framework only utilizes input parameters and internally determine if the parameter is meant to write information to the Data Table for other components to use or if the parameter is meant to give an input to the application. you may enter an alternate path to the SAP Login. Technical Note: SAP Test Acceleration and Optimization provides different ways to create a screen either by using the metadata or creating objects during execution (runtime). The default is: “Windows_system_root\temp”. you may enter an alternate path to the Windows temp directory.6 Expert Settings 1. Some screens within SAP could be empty containers for dynamically added content (This content may be a screen or a field depending on the programmer needs). These screens are visible in SAP Test Acceleration and Optimization.3 Connections 4. 3. 4. If an object is displayed of hidden during runtime then the metadata inspection will not be able to adjust to this change. 4. In the SAP Login.ini file. Display Information Box will enable a small information box that will enable you to check for further messages of SAP Test Acceleration and Optimization 2. but SAP Test Acceleration and Optimization is not able to display them in Inspect module As one of the features in SAP Test Acceleration and Optimization.1 Usage of SAP Quality Center/QuickTest Professional Output Parameters SAP Quality Center and QuickTest Professional provide input and output parameters for passing data from one component to the other. This may cause the inspection method to return an error when inspecting certain screens.ini text box. There are screens that can be accessed manually.1. but SAP Test Acceleration and Optimization cannot create test components out of them by design.2. <August 2008> 27 .2 Working with SAP Test Acceleration and Optimization (Hints and FAQ) 4.2 SAP Test Acceleration and Optimization Inspection SAP Test Acceleration and Optimization is not populating all the screens associated with TCodes in the Inspect module.

1. Grids and trees are not supported on either approach UI Scanner or Introspection.2. The UI Scanner approach is designed to capture up to 80% of the objects in an SAP system.5 How to Create own Components using SAP Test Acceleration and Optimization The SAP Test Acceleration and Optimization framework is meant to provide clients the capability to expand its use outside of the components provided during implementation.3 Connections 4. If some functionality that already exists on the framework were to be modified then the original function should be copied into the CBASE_Custom_Wrappers. Some useful tips to make performance better are: Make sure to use the initialize script (preconfigured test component) in every new test 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. This will allow SAP to provide better support and keep a standard framework. This guide includes a list of the functions that are available with the framework as well as best practices around the creation of new functions and functionality within the framework. FieldValue.3 Performance during Test Execution There is a major performance issue during the execution of the test script.4 SAP Test Acceleration and Optimization/UI Scanner not capturing Grid Tables SAP Test Acceleration and Optimization / UI Scanner is not capturing the grid table and other objects on the standard SAP screens. Standard Wrapper layout example: Sub SAP_Wrapper_Name(FieldName. Grids and tables are highly dynamic objects that can be customized and adapted for each user interacting with that screen. ReportingName End sub 28 <August 2008> . FieldValue. this file should be the only one containing customized client functions.vbs” file. It is by design that grids. If you are using SAP Quality Center as a central repository on the network there is a performance issue which will cause the execution to become slower than if we were executing the process manually. Any change that needs to be done as a customer modification has to be done in the “CBASE_Custom_Wrappers. ReportingName) SAP_Wrapper_Name_Location FieldName. One of the documents provided with the SAP Test Acceleration and Optimization install is the SAP Test Acceleration and Optimization RTL Documentation. trees and similar objects are not supported for scanning. Performance issues are most of the time related to network configuration and the number of times that the network is being accessed.vbs file and modified here.2. 4.2.

2. In order to change this functionality. FieldIndex. To remove this behavior. ReportingName & “ = “ & FieldValue CheckErrorHandler() End sub 4. change the setting under Configuration -> Import/Export -> Overwrite Components Mark the check box if you want the tool to overwrite the uploaded component and if you want a serial number to be added in case you don’t want it to be overwritten leave it OFF.6 SAP GUI Window Change Size on Execution The SAP Test Acceleration and Optimization framework includes resizing functionality that will re-size the screen to allow the user to view QuickTest Professional. ReportingName) On error Resume Next Dim OBJ SET Obj = SAP_GetObject(FieldName. QuickTest Professional identifies the texts in the status bar as item1. A list of keywords is: For item1: <August 2008> 29 . SAP and any other window while in execution. add the following code to the CBASE_Custom_Wrappers.Method FieldValue ReportLog “INFO”. item2. “Step Description”. “FIELDTYPE”. some customer find this design uncomfortable.3 Connections Sub SAP_Wrapper_Name_Location(FieldName.2.7 Overwrite Prompt in BCIE A feature of SAP Test Acceleration and Optimization is the ability to overwrite components each time one is uploaded.2. The relevant information will be stored most of the times in item2 and there are keywords that help SAP Test Acceleration and Optimization identify what you are looking for.8 Record Number When you want to save a number that comes from the status bar SAP Test Acceleration and Optimization will need to know which document you are looking for. FieldIndex. FieldValue.vbs file: sub ResetAppPosition(App) End Sub 4.”SET/GET”) OBJ. 4.

10 Creating GET Components SAP Test Acceleration and Optimization 1. PROMOTIONORDERNUMBER. QUOTATIONNUMBER. PURCHASE_ORDER_NUMBER. 4. TO_NUMBER. CUSTOMER_NUMBER. SAP Quality Center test plan naming conventions and component naming convention prevent some characters from being used either on the component name or the parameters name.vbs” and make the necessary changes. QUOTATION_NUMBER. CANCELLED_DOCUMENT_NUMBER. PURCHASE_REQUISITION_NUMBER. PURCHASE_ORDER_NUMBER.2. MATERIAL_DOCUMENT_NUMBER. " Ä Ä Ö ß Ö Ü ü spaces @ % * [ / & ' . To enable this functionality go to the configuration link and to the inspect tab: ) # ^ + ] { | : ! $ & = \ } . In order to extend the keyword functionality. VALUE_CONTRACT_NUMBER.vbs” to “CBASE_Custom_Wrappers.9 Character Removal from Test Plan Name During consolidation some characters are removed from test plan name to be consistent with the SAP Quality Center functionality. PRNUMBER For item2: CUSTOMER_CREATED_FOR_COMPANY_CODE. please copy/paste the function Get_Status_Item from “CBASE_SAP_47_Wrappers.2. SALES_ORDER_NUMBER. INQUIRYNUMBER. Having this in mind some characters are removed from component names: 4. GROUP_NUMBER. MATLRELVALUECONT. SALESDEALNUMBER. DOCNUMBER.0. INBOUND_DELIVERY. DOCUMENT_NUMBER. OMSHARDWARESALESNUMBER. PROMOTIONNUMBER. STANDARDORDERNUMBER. 30 <August 2008> . RFQ_NUMBER. ITEMPROPOSALNUMBER.10 presents a new feature that allows the creation of components to get data from the screen. INQUIRY_NUMBER If a word that is not listed here is used then by default the item2 will be used to capture the value. OEMSALESNUMBER.3 Connections BILLING_DOCUMENT.

4.2. 4. this means that all the parameters in a get component will be DT_ values. the parameter name needed is DISABLE_EXTENDED_STORAGE.0.10 needs one site admin setting in the SAP Quality Center server. TAO also required the computer where it will be installed to have a valid SAP GUI Installation. Naming convention on get components is the same as set components but with a postfix of _GET at the end of the name. <August 2008> 31 .11 SAP Quality Center Required Settings SAP Test Acceleration and Optimization 1. Regardless of the component type selected all the other settings will determine the behavior of the application.12 Setup Options SAP Test Acceleration and Optimization installation package requires that the computer where it will be installed has a valid SAP Quality Center connection before SAP Test Acceleration and Optimization allows it to be installed. Get components will provide the ability to save any value of the supported objects by storing it to a data table field (DT_). More documentation on this parameter and how to add this to the server can be found in the SAP Quality Center admin’s guide. Then you can either use these values to make a comparison or to input that into another field.3 Connections The component type check boxes will determine the type of components that will be create.2. there should always be one selected.

Close all Internet Explorer browsers (because the SAP Quality Center QTA API is attached to an IE Session) 2. too) these steps are quite useful. but please keep in mind that a valid operation without the SAP Quality Center OTA API is not possible. Connect to the SAP Quality Center server that SAP Test Acceleration and Optimization will be interacting with via Internet Explorer. This will enable SAP Test Acceleration and Optimization to work with that specific version of SAP Quality Center.exe NOREQ=TRUE Note the blank space between setup.2. 4. When working with consolidation 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 by another user or yourself. Close all SAP Quality Center connections made from this computer 5. 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 Plan module.2. In order to do this: 32 <August 2008> .13 Consolidator Notes SAP Test Acceleration and Optimization consolidation works directly with the SAP Quality Center OTA API and this enables to work at a back end level. Especially if you are working with different versions of SAP Quality Center (and every version might have a different SAP Quality Center OTA API version. 4. the way to achieve this is to open a command line prompt and call the SAP Test Acceleration and Optimization setup file with the following parameter: C:\TAO Install###BOT_TEXT###gt;setup.15 Changing the Log File Path SAP Test Acceleration and Optimization provides the capability of changing the log file path and also the log file name. The 2 items mentioned above could damage the consolidation process and then a reconsolidation will need to occur in order to fix the issues. Make sure SAP Test Acceleration and Optimization is closed 4.3 Connections In some cases you may want to avoid those verifications.2. 4. Once SAP Test Acceleration and Optimization is installed in a computer the first steps to make the environment work properly: 1. This will download the SAP Quality Center OTA API file from the SAP Quality Center server to your workstation.exe and NOREQ=TRUE This will install SAP Test Acceleration and Optimization. Make sure QuickTest Professional is not open 3.14 After-Installation Notes The following steps are needed while working with the SAP Quality Center OTA API. Don’t forget to change/check the SAP Quality Center version in SAP Test Acceleration and Optimization connect module.

2. 4.3 Connections 1. 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. This is a known issue that occurs within SAP Test Acceleration and Optimization in combination 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.16 Component Folder inside SAP Quality Center SAP Test Acceleration and Optimization is creating a component folder inside SAP Quality Center. Select the Log tab: 3. Workaround: <August 2008> 33 . Select the configuration link on the top right of SAP Test Acceleration and Optimization: 2. In the log location section you can specify the path and name of the SAP Test Acceleration and Optimization log.

Select New -> Application Area 4. 34 <August 2008> .3 Connections “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 a reference. Please check at local HP support for further patches.3.2 will require the following patches: QTP92P1713.exe This fix will revert back the spy functionality to the default one. Make sure that the SAP and Web add-ins are selected 5. 9.0. Save the Application Area with the name “_SAP_Doc” This procedure will enable all the components created by SAP Test Acceleration and Optimization to execute and work properly.1 and 9.exe This patch is only required if working with SAP GUI 7.To create this “application area” follow the next steps: 1.3 Working with QuickTest Professional (Hints and FAQ) 4.3.1 Both patches are available at your local HP support representative. 4. QTPSAP82P8116. allowing inspection to work on popups.2 Creating an Application Area in QuickTest Professional SAP Test Acceleration and Optimization components require an application area that contains the QuickTest Professional SAP add-in and the web add-in. 4.1 QuickTest Professional Required Patches QuickTest Professional version 9. Open QuickTest Professional 2. connect to the SAP Quality Center project through QuickTest Professional 3.

5. (Optional) 4. 6.1. Inspection allows you to import transactions for your business process test. This function will fill the list of transactions accordingly. 5.3 Add a Transaction SAP Test Acceleration and Optimization allows you to add one transaction code at a time. 3. The Add Transaction pop-up window opens. To add a transaction code 1. You can always define dynamic or consumable data in a separate process. Enter a description for this code in the Description field. Information. Click Add .1.1 About Inspection Inspection is the most powerful feature in SAP Test Acceleration and Optimization. If a business process loops. 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. 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 SAP back end system configured correctely) automatically by SAP Test Acceleration and Optimization. The Transaction Code appears in the Transaction List. Click Add.5 Typical Use Cases 5 Typical Use Cases 5. Ignore). or deviates from the logic of the first iteration. <August 2008> 35 .2 Using Inspection to Select Transactions Open the Inspection screen from the SAP Test Acceleration and Optimization navigation bar. Use inspection to: Select transactions from a list of current transactions Add new transactions to the current transaction list Send the transactions to SAP Quality Center server and/or a designated directory One Business Process When planning a business process test. When you specify a business process. simply select the function “Get weighed list of most used transactions”. 2. Ultimately. each business process translates into one test script. Repeat these steps for each transaction code you want to add. Warning. has inputs or branching logic.1 Inspection 5. specify as much static data as possible within the business process definition.1. 5. Select an Importance level from the pull-down list (Business Critical. split the process into multiple tests. Enter a transaction code. consider that SAP Test Acceleration and Optimization can generate one business process test at a time.

Inspection determines if the transactions are valid. A valid transaction contains screen objects that connect to metadata. To select all the screens. To perform inspection 1. The Remove icon (an X inside a circle) appears. 5. please ensure that NO screens are selected for this transaction in the right part of the window. To select one or more screens associated with a transaction code. 3.5 Perform Inspection The inspection screen displays a group of transactions and associated screens. 2.5 Typical Use Cases 5. select the Transaction Code in the Transaction List. Click the left column. The transaction code is removed from the list. Important: if you wounld like to remove a transaction. or data stored in tables. 4. 36 <August 2008> . 2. Select the transaction code you want to delete. A confirmation dialog appears to remove the specific transaction code. You will not be able to navigate to there unless you add the same transaction code again. You may select one or more SAP transaction code combinations as required by your business processes.1. The screen associated with this transaction code opens in the Transaction List. To remove a transaction 1. and sends them to SAP Quality Center.4 Remove a Transaction SAP Test Acceleration and Optimization permits you to remove one transaction at a time. click the Check All link at the bottom of the screen. Click Yes.1.

reinspect any screens that failed. Use the UI Scanner to capture the screen. click the View All link in the Run Inspection box. To choose specific screens. Note SAP Test Acceleration and Optimization may not recognize screen objects that are dynamically generated in code or are tagged as (empty container screens). All three columns must contain an “OK” for the screen to successfully upload to SAP Quality Center. select the checkbox beside each screen. To view a list of the transaction codes and screens you have selected. go back and select each transaction code that you want to change and deselect the box. Send the screen to SAP Quality Center. 7. If these screens continue to fail: a. 5. b. Repeat steps 1–3 to add additional transactions. CompCreatorResult (the directory you specified to save inspection results). <August 2008> 37 . Click Inspect. You can print out this list. Scroll to the right in the Results Window and review the three columns: Inspection Result. 8.5 Typical Use Cases 3. and the Upgrade Result. 6. To remove a screen. 4. If one or more screens fail Inspection.

Wait for the “Done” message. SAP Test Acceleration and Optimization and QuickTest Professional. Navigate to SAP Test Acceleration and Optimization inspection -> UI Scanner 3. Click Launch UI Scanner. 2. To run UI Scanner 1. Open the newly scanned transaction code in SAP Quality Center and add it to an existing or a new script.6 Using the UI Scanner The UI Scanner is an add-on for QuickTest Professional. 5.5 Typical Use Cases 5. 6. Name and Save the transaction code window.1. 4. It scans most of the data in the screen and is less restrictive than inspection. Minimize all the windows on your computer except the screen that you want to scan. The UI Scanner sends the screen to SAP Quality Center. The UI Scanner is able to detect the open SAP GUI sessions and will show them in the SAP Test Acceleration and Optimization UI. 38 <August 2008> . The UI Scanner opens the captured transaction code in QuickTest Professional.

such as clicking on the New or OK button. Click Authenticate.2. 3. Click HP Quality Center on the HP Quality Center server homepage. c. Click Tests. Use the Test Plan section in Business Components to build a test script. b. You can add these buttons as separate components during the script building process. An ideal component contains a small number of operations and can function independently. To create a new folder: a. 3. 5. 2. whenever a user clicks a Query button. On the upper right corner of the SAP Test Acceleration and Optimization client.2 Building Test Scripts in SAP Quality Center Note: The following explanations briefly outline the typical use case. For example. Select New Folder.5 Typical Use Cases 5. therefore it is makes sense to group these together in a component. On HP Quality Center homepage. The component definition only contains the steps required to complete the form or applet. It does not include application logic.2. To build a test script 1. enter your user ID and password. click the SAP Quality Center link to open the respective homepage. 2.” HP Quality Center automatically completes the fields with your domain and project and logs you in. followed by clicking GO. An example of a SAP Test Acceleration and Optimization component is entering an activity. 4. To log on to SAP Quality Center 1. This section describes only SAP Quality Center buttons and actions that you use to build test scripts. If you checked “Automatically log in to my last domain and project on this machine. you have verified that your business processes work and have split them into logical components. SAP Test Acceleration and Optimization components should not contain flow logic or operations that span multiple SAP screens or views. the next step requires the user to perform the query. Refer to the SAP Quality Center documentation for information about other functionality. Click Test Plan. 5. Navigate from Business Components to Test Plan in SAP Quality Center.1 Logging onto SAP Quality Center You must be an SAP Quality Center project administrator to use SAP Quality Center (also referred to as HP Quality Center). an application that provides many test management functions. but are not able to replace deep SAP Quality Center knowledge Building your SAP application test scripts requires the SAP Quality Center. At this point. Some operations are always performed together. Enter a name for the folder. <August 2008> 39 .2 Building a Test Script Use the Test Plan module in SAP Quality Center to build a test script.

and transactions as needed to create the test. Navigate to the SAP actions and buttons. 5. 40 <August 2008> .3 Parameterizing the Elements Parametrization allows a business component to receive data from an external source. Parameterizing the Elements in the Test Script. All parameters that you intend to store in the Excel spreadsheet must use the DT_ prefix. When you hard code a value into a parameter. Select New Test. If you parameterize a value. SAP Test Acceleration and Optimization reads the new value from the spreadsheet each time you re-execute this script. Select the folder where you want to save the test. or to return data for use in other components. c. You can store the parameterized elements in an Excel spreadsheet or in the SAP Quality Center database. Select Business Process from the pull-down test type. b. 4. To create a new test: a. For example. d. the SAP Quality Center server inserts this exact value each time it encounters this parameter in a test script. Click OK. for more information. The initialization script that you create in the SAP Quality Center server Test Plan specifies the name of the associated spreadsheet. Once you have verified the elements. Open the Actions folder and navigate to Initialize Script. but do not include the DT_ prefix. SAP Test Acceleration and Optimization provides an Excel spreadsheet mechanism to store parameters.5 Typical Use Cases d. you may parameterize elements or proceed to the next chapter to consolidate the test script. the value becomes static or hard-coded. Initialize Script adds a link in the test script title to the Excel spreadsheet. 7. Designate a value as hard-coded when it stays the same from one execution to the next. To create a SAP Test Acceleration and Optimization parameter entry 1. Open the test script that you want to parameterize. 8. the test name. you can create a function to update it. verify that you have added all the necessary elements in a logical order. The Details tab displays your name. 2. After you build the script. Click the Test Script tab to build your script. The DT_prefix parameters are useful for storing and creating variables that change from execution to execution. Use the small disk icon. Save the test. A pop-up dialog box opens. 3. and the status. Click OK. e. Use drag and drop commands. Enter the value and include the DT_ prefix to the data value name. Enter a name for the Test. By storing the parameter in an Excel spreadsheet. 6. buttons. The Components Iteration window opens. 5. the creation date. a payroll application may include a current date that changes from week to week.2. A components tree opens in the right column. Click the data value that you want to parameterize. Make the first component in the test plan Initialize Script if you plan to parameterize the values in this script. See the next section. Navigate to the location on the components tree where your transactions are stored.

3 Consolidating Test Scripts in SAP Quality Center Consolidating creates one component from the elements in your test script. (Optional) You may enter an description for this value. (Optional) You may enter an description for this value. A message at the bottom of the screen details the Consolidation progress. 2. 5. 6. Select the test script you want to consolidate and click Consolidate. Click OK. Choose the Select a Test Plan tab. 6. Click the data value that you want to parameterize. 3. Make sure to save the test script in the SAP Quality Center. 4. the components are saved in a designated folder in the SAP Test Acceleration and Optimization system. Enter the value.5 Typical Use Cases 4. To create a hard-coded parameter entry 1. 4. <August 2008> 41 . Click OK. The new component contains all the code and screen elements from the test script.1 Consolidating Test Plans When you save a test script in the SAP Quality Center. 2. or whether you want to save it for reuse. 5. Open the SAP Test Acceleration and Optimization client and click Consolidate. 6. Specify whether this value is output for use in another component. 5. Follow these six steps to parameterize as many values as required. Open the test script. Navigate to the folder where you saved your test script. To consolidate in the SAP Test Acceleration and Optimization client 1. 3. 5. 5. The Components Iteration window opens. Specify if this value is output for use in another component or whether you want to save it .3.

The business processes that use this component appear in a table below the test component. navigate to the test component you want to consolidate.2 Consolidating Selected Components Use this screen when you update a component and need to propagate the update to multiple business processes. The user is now able to select which of these tests he wants to reconsolidate with the check boxes to the left of each business process.) Example: If Component 1 is modified and it is used in 10 business processes.3. 3. click the Select by Component tab. Consolidate by components: This feature enables you to consolidate all or some of the tests that use a given component. using this feature will enable the user to select Component 1 from the list of components (left hand side of the screen) and the business process list will be populated by all 10 tests that use this component. (The list represents all the business processes using the selected components.5 Typical Use Cases 5. 2. On the Consolidate page. When the user clicks the Consolidate button all the selected tests will be consolidated. Click the test component. This provides the ability to consolidate several business processes from a list that is generated after a component is selected. In the tree view. 42 <August 2008> . To consolidate selected components: 1.

The user interface is useful for manual maintenance activities.4 Importing and Exporting Components The Import and Export module primarily works in the background any time you transfer components between the SAP Test Acceleration and Optimization client and SAP Quality Center server. or from one server to another Download components from SAP Quality Center. Select the business processes you want to update with the new information.1 Exporting Test Components When you export a component from SAP Test Acceleration and Optimization to the SAP Quality Center. 5. the component gets stored in the file that you designated in Connections. 5. Click Consolidate.5 Typical Use Cases 4. Transport components from one SAP Quality Center server project to another. In the SAP Test Acceleration Optimization navigation bar. 5. Deselect a business process if you do not want to reconsolidate it. Navigate to the directory in the SAP Test Acceleration Optimization directory. To export components from the SAP Test Acceleration and Optimization 1.4. click Import/Export . <August 2008> 43 . You may want to transfer components to: Back up components on the SAP Quality Center server or on a hard drive. There is no limit to the number of components you can import or export. 2.

4. 5. 6. 4.2. 5. The status bar indicates the export’s progress. Click Export to SAP QC.4. 5. In the SAP Test Acceleration and Optimization navigation bar. 2. you can store the component in any location for which you have persmission. Navigate to the directory you want to import from on the SAP Quality Center. click Import/Export. A Browse For Folder popup opens. Select the checkbox next to the transactions that you want to export to SAP Quality Center. Click the box next to each of the components you want to transfer. If you need to make a new folder: 44 <August 2008> . Importing Test Components When you import a component from the SAP Quality Center.5 Typical Use Cases 3. Check the designated folder on the SAP Quality Center to make sure the Export succeeded. Browse to the folder where you want to store the components. 3. Click Import From SAP QC. To import components from the SAP Quality Center 1.

browse to the folder or directory where you want to make a new folder. A new unnamed folder appears in the directory. <August 2008> 45 . b.5 Typical Use Cases a. 8. Make sure that the new folder exists and that it contains the exported components. Click Make New Folder. Enter a name for the new folder 7. Click OK. In the Browse Window. c.