SAP TAO Guide.pdf

8/10/2019 SAP TAO Guide.pdf

http://slidepdf.com/reader/full/sap-tao-guidepdf 1/143

How-toSAP TAO 3.0 SP2

January 2014

PUBLIC

How-to GuideSAP Test Acceleration and Optimization (SAP TAO)



Remove a step ................................................................................................................................................. 5410.4

Pause ............................................................................................................................................................... 5510.5

Dockable view mode ....................................................................................................................................... 5510.6

Test Component Generation .......................................................................................................................... 5510.7

10.7.1 Using SAP TAO Inspection ....................................................................................................................... 55

10.7.2 Using SAP TAO UI-Scanner ...................................................................................................................... 56Test execution in SAP TAO Run and Report .................................................................................................... 5810.8

10.8.1 Displaying Run and Report-relevant Data ............................................................................................... 58

10.8.2 Adapting SAP TAO Run List Settings ........................................................................................................ 59

10.8.3 Pausing a run list ..................................................................................................................................... 60

TBOM creation in SAP TAO Run and Report ................................................................................................... 6010.9

10.9.1 Basic configuration for TBOM creation by TAO ...................................................................................... 60

10.9.2 Project specific configuration for TBOM creation by TAO ...................................................................... 64

10.9.3 Actually creating a TBOM with SAP TAO ................................................................................................. 67

Consolidating Tests ..................................................................................................................................... 6910.10

10.10.1 Select by Test ...................................................................................................................................... 70

10.10.2 Select by Component .......................................................................................................................... 73

Using Change Analyzer ................................................................................................................................ 7410.11

SAP TAO Repository .................................................................................................................................... 7610.12

10.12.1 Displaying Components ...................................................................................................................... 76

10.12.2 Displaying PFA Recordings .................................................................................................................. 76

10.12.3 Repository Synchronization ................................................................................................................ 77

Identifying Properties of UI Elements Using Object Spy ............................................................................. 8010.13

10.13.1 Spying an ALV control ......................................................................................................................... 84

SAP TAO Log ................................................................................................................................................ 8410.14

10.14.1 Accessing Logs From SAP TAO Frontend ............................................................................................. 85

10.14.2 Accessing SAP TAO logs (log xml file) .................................................................................................. 87

11 Example for Test Case Creation .............................................................................................................................. 88

Test Case Creation for “Create Sale Order” .................................................................................................... 8811.1

11.1.1 Performing a Process Flow Analysis for Create Sales Order Transaction (VA01) ................................... 88

11.1.2 Uploading the Process Flow Analysis of Create Sales Order Transaction (VA01) ................................... 92

11.1.3 Storing the Sales Order Number in the Data Table Excel Sheet ............................................................. 96

11.1.4 Adding Manual Validation on the Status Bar .......................................................................................... 96

11.1.5 Consolidation of the Create Sales Order Test Case ................................................................................ 97

11.1.6 Executing the Create Sales Order Test Case and Viewing HP QuickTest Professional Execution Logs .. 9811.1.7 Viewing SAP TAO Logs ........................................................................................................................... 102

Test Case Creation for “View Sales Order” ................................................................................................... 10211.2

11.2.1 Performing Process Flow Analysis of the “View Sales Order” Transaction (VA03) ............................... 102



11.2.2 Uploading the Process Flow Analysis of “View Sales Order” Transaction (VA03) ................................ 104

11.2.3 Consolidating the Create “View Sales Order” Test Case ....................................................................... 104

Creation of a Composite Test Case ............................................................................................................... 10511.3

11.3.1 Creating a Composite Business Process Test Case and use Single Data file ......................................... 105

11.3.2 Creating a Composite Business Process Test Case and use Multiple Data files ................................... 111

12 Repairing SAP TAO Test Cases ............................................................................................................................... 113Introduction to Different Change Types ....................................................................................................... 11312.1

Repairing Test Cases Due to Customizing Changes ...................................................................................... 11412.2

Repairing Custom Code Changes .................................................................................................................. 11612.3

13 Example for Test Case Repair ................................................................................................................................ 117

Repair Using BPCA Integration ...................................................................................................................... 11713.1

13.1.1 Customizing Change - PO Number has become mandatory in VA01 transaction ................................ 117

13.1.2 Custom code change – New input field is introduced in Custom VA01 transaction ............................ 122

Repair without BPCA Integration .................................................................................................................. 12413.2

13.2.1 Customizing Change - PO Number has become mandatory in VA01 transaction ................................ 124

13.2.2 Custom code change – New input field is introduced in Custom VA01 transaction ............................ 129

14 Known Limitations ................................................................................................................................................ 133

15 Advanced ............................................................................................................................................................... 134

Login Schema ................................................................................................................................................ 13415.1

15.1.1 Login Schema Structure ........................................................................................................................ 134

15.1.2 Post-login Steps ..................................................................................................................................... 135

15.1.3 Login Schema Definition ....................................................................................................................... 135

16 FAQ ........................................................................................................................................................................ 140

TBOM Creation .............................................................................................................................................. 14016.1

Miscellaneous ............................................................................................................................................... 14016.2

17 Appendix ............................................................................................................................................................... 141

Citrix and SAP TAO ........................................................................................................................................ 14117.1

SAP TAO and ALM 11 (SAP Quality Center by HP 11) ........................................ Error! Bookmark not defined. 17.2

Component for Support Messages ............................................................................................................... 14217.3

See Also ......................................................................................................................................................... 14217.4



of 143

2 Introduction

The SAP Test Acceleration and Optimization application supports customers in automating their business processtests by automatically generating draft test cases and test components. Its tight integration with SAP SolutionManager helps in identifying the impacted test cases and components when there are changes in the landscape. TheSAP Test Acceleration and Optimization application creates modular test cases, which are easy to maintain, whenthe test cases are damaged due to functional changes.

In the face of continuous, accelerated change in the business environment, there is an increasing demand forinnovation and an increased frequency of change in business applications. Any change to your solution landscaperequires testing to ensure software quality and minimize business and IT risk. But since so many testing tasks requiremanual effort, quality assurance teams find themselves pressed for time. To stay on schedule, teams must ofteneither delay the release or skip critical tests. Even if testing activities are automated using traditional tools, itbecomes difficult to maintain these scripts. This leads to higher cost or risky testing process.

In order to effectively address the above mentioned challenge, SAP offers the SAP Test Acceleration andOptimization application, which helps you in quick creation of automated test cases using reusable components.

The SAP Test Acceleration and Optimization application supports customers in automating their business processtests by automatically generating draft test cases and test components for SAP GUI –based transactions, SAP CRMWebClient, SAP NetWeaver Portal, ABAP WebDynPro, Java WebDynPro, Business Server Pages and HTMLBapplications. Using this application in combination with the SAP Quality Center by HP application by HP, you canmodify, compose and execute automated business process tests in SAP software development and test systems. TheSAP Test Acceleration and Optimization application also provides a lot of reusable library components, which couldbe used for test composition.

SAP Test Acceleration and Optimization helps you change the testing paradigm from manual testing to testing bycomposition, thereby reducing the costs and risks for testing SAP solutions. The benefits include reduced effort formaintaining automated business process tests, reduced risk due to better testing coverage, increased capacity toabsorb and manage change, and tight integration with the SAP Solution Manager. The tool is tightly integrated withSAP Solution Manager’s Business Process Change Analyzer functionality to report impacted test cases andcomponents due to changes in landscape.

SAP Test Acceleration and Optimization helps in quick creation and maintenance of test cases, which leads to highertest coverage, at a very less cost compared to manual testing and shorter testing cycles. The efficiency you gain canreduce costs, increase speed, and more importantly, help minimize the risk of outages and other problems caused bypoor testing.



of 143

Return on investment for the SAP Test Acceleration and Optimization application is much faster than traditionalautomation, as the test case generated by it are easier to maintain because of their modular nature. If comparedwith Manual Testing, the crucial benefit is SAP Test Acceleration and Optimization automated scripts require veryless effort to execute, and so is the savings in the resource utilization.

3 Scope of documentThis document is based on SAP TAO 3.0 SP02. Any reference or description of older releases is explicitly mentionedand described as is.



of 143

4 Supported UI TechnologiesSAP TAO 3.0 SP02 supports automation of following UI Technologies:

Technology Version supported by SAP TAO 3.0 SP03

SAP GUI SAP GUI 7.30 onwards

SAP CRMCRM 7.0 SP02 onwards, CRM 7.0 EHP1 SP03 onwards,CRM 7.0 EHP 2 (All service packs)

ABAP WebDynPro NW 7.02, 7.30, 7.31, 7.40 onwards

SAP NetWeaver Portal(SAP NW Portal) NW 7.30 onwards

Business Server Pages(BSP ’s) Any version (manual update in the test)

HTML Business(HTMLB) Any version (manual update in the test)

SAP GUI for HTML(Web GUI) NW 7.31 onwards

Java WebDynPro(JWD) NW 7.31 onwards (Some support for 7.02 onwards)



of 143

5 InstallationFollowing are the Prerequisites

SAP solution manager has installed with correct patch

SAP TAO Back end(ST-TST) with right version in SAP Solution Manager

ST-PI with right version SAP front end

HP QTP installed with right version and patches

HP QC installed with right version and patch

6 UpgradePlease refer to SAP TAO Administration Guide at http://service.sap.com/saptao -> Important Links

7 ConfigurationFor HP ALM and HP QTP, please refer to the Administration Guide at http://service.sap.com/saptao -> ImportantLinks

Please refer below solution manager configuration for TAO.

Go to SOLMAN_WORKCENTER

Go to “SAP Test Acceleration and Optimization ”

7.1.1 Check Prerequisites

In the scenario SAP Test Acceleration and Optimization (TAO), you configure the generation of automatic tests andthe parameterization of components for functional testing of SAP solutions.

http://service.sap.com/saptao









of 143

In this step, the completeness of the configuration scenarios System Preparation and Basic Configuration is checked,which are a prerequisite for the setup of TAO.

1. In the Documentation column, choose Display and read the information about the automatic activities.2. Be sure you are in Edit mode.3. To check prerequisites, choose Execute All or Execute Selected .4. Check the status and the results in the log.5. If there are errors, choose the link in the Navigation column.6. The required activity opens in a new window. Complete the activity and close the new window.7. Under Automatic Activities and under Log, choose Refresh .8. Check the messages and read the Details information for the errors.9. Set the Execution Status :

o If the activity was performed successfully, select Manually Performed .o If an error occurred and the activity must be performed again, select Manually Performed with Errors .o To postpone activity, select Postponed .

10. Choose Next .

7.1.2 Create User

In this step, you create standard users in the SAP Solution Manager system, required for SAP Test Acceleration andOptimization (TAO). You can create new users or enhance existing ones.

1. Be sure you are in Edit mode.2. Under Action , select what to do with an existing user or to create a new user. If required, assign an initial

password.You can also assign a user to a user group: Choose the Edit icon next to User Group and enter a user group. Thesystem adds it to the user in the user maintenance (transaction SU01).You can also create a new user group: Choose Create User Group to open a maintenance window for usergroups (transaction SUGR).

3. Define the role assignment. For details, choose Display in the Role Description column.4. Choose Execute . The system assigns the needed roles.5. Check the log.6. Choose Next .



of 143

Note:

If an SAP role already exists, the system marks this role assignment for update, after you haveexecuted the user and the role assignment, even though all roles are correctly assigned. Check theother copies of the SAP role for necessary updates.

All users and user roles are only templates. If your user definitions and processes are different,adapt the users and user roles (authorizations) accordingly.

For more information, see the Security Guide for SAP Solution Manager underhttp://service.sap.com/instguides -> SAP Components -> SAP Solution Manager <current release>.

7.1.3 Select System Under Test

In this step, select the systems under test (SUT). These are the technical systems on which you want to perform testactivities, such as Process Flow Analysis, Inspections, and Execution.

1. Be sure you are in Edit mode.2. Select one or several systems that you plan to use for testing.3. Choose Next .



of 143

7.1.4 Select Client

In this step, select the clients of the technical systems that you selected in the previous step.This is mandatory because some settings for SAP Test Acceleration and Optimization are client-dependent.

1. Be sure you are in Edit mode.2. For each system, select one client from the drop-down list.3. Choose Next .

Note:

Only clients with a working READ RFC destination are displayed for selection.

To have clients ready for selection, you must have configured the technical system in ManagedSystem Configuration of the SAP Solution Manager: Configuration work center.



of 143

7.1.5 Select UI Technologies

In this step, specify the user interface technologies that are used on the selected technical system that is to be usedas system under test.

Only select the required UI technology to avoid unnecessary checks. If, for example, your system under test is not aSAP CRM Web system, you do not run a CRM scenario and do not need to check if CRM notes are correctly

implemented.

1. Be sure you are in Edit mode.2. Set the checkmark for the relevant UI technologies.3. Choose Save and Next .



of 143

7.1.6 Configure System Under Test

In this step, configure the system under test (SUT) so that SAP Test Acceleration and Optimization (TAO) can access itfrom the SAP Solution Manager system. The step includes manual and automatic activities:

Checking that the required SAP Solution Manager plug-ins (ST-PI, ST-A/PI) are installed and updated on the

SUT, and that a required SAP Note is applied. Enabling SAP GUI Scripting so that SAP TAO can run a Process Flow Analysis on the SUT. Creating or updating technical users that are used by SAP TAO to collect testing information from the SUT. Creation of destinations between SAP Solution Manager and the SUT.

Choose Next to proceed with the first sub-step.

7.1.6.1 Check Prerequisites

This step checks if the required SAP Solution Manager plug-ins are installed on the system under test:

ST-PI: for all activities and all UI technologies ST-A/PI: for the automation of SAP CRM Web UIs (starting with CRM 7.0)

If tests in a SAP CRM Web UI are planned, this step also checks if the system has been updated with the required SAPNote.

1. Be sure you are in Edit mode.2. Choose Execute All or Execute Selected .3. Check the log. For a solution of errors, check the message texts and choose Display in the Documentation

column and read the information.4. Set the Execution Status :


5. Choose Next .



of 143

7.1.6.2 Enable Scripting

In this mandatory step, you manually enable SAP GUI scripting on the system under test and on desktops. This isrequired for Process Flow Analysis and test execution of SAP GUI-based applications.

1. Be sure you are in Edit mode.2. Choose Display in the Documentation column and read the information.3. Follow the descriptions from the documentation, and choose Start Transaction to start.4. Set the Execution Status :


5. The enabling of SAP GUI Scripting on the desktop has to be done in SAP GUI on the desktop. For moreinformation, choose Display in the Documentation column and read the information.

6. Choose Next .

7.1.6.3 Create Technical User

1. Be sure you are in Edit mode.2. Select a user of the system under test.



of 143

3. Under Action , select what to do with an existing user or to create a new user. If required, assign an initialpassword.

4. You can also assign a user to a user group: Choose the Edit icon next to User Group and enter a user group. Thesystem adds it to the user in the user maintenance (transaction SU01).

5. You can also create a new user group: Choose Create User Group to open a maintenance window for usergroups (transaction SUGR).

6. Select the following roles to be assigned to the technical user (for more information, choose Display in the RoleDescription column):

o SAP_CRM_TST_RFC: for SAP CRM-based SUTs

Download this role from your SAP Solution Manager system and upload it to your CRM system. Maintainthe authorization objects, generate the profile, and execute the user comparison.

o SAP_TST_AGENT_RFC: for communication between SAP Solution Manager and the SUT.o SAP_WDA_TST_RFC: for automation of the UI technologies Web Dynpro ABAP, Web GUI, SAP UI5, and

Business Service Pages.

Download this role from SAP Note 1780855 and upload it to your SUT.

7. Choose Execute . The system assigns the needed roles.8. Under Users , choose Test to test the login.9. Check the log.10. Choose Next .

For more information, see the Security Guide SAP Solution Manager , at http://service.sap.com/instguides

-> SAP Components -> SAP Solution Manager Release 7.1 -> Authorization Concept for SAP Solution Manager .

7.1.6.4 Create Destination

1. Be sure you are in Edit mode.2. Choose Display in the Documentation column and read the information.3. Choose Execute All .4. Set the Execution Status :

o If the activity was performed successfully, select Manually Performed .o If an error occurred and the activity must be performed again, select Manually Performed with Errorso To postpone activity, select Postponed .

5. Choose Next .



of 143

7.1.7 Enhance Configuration for TBOM

You perform this step only if you use TBOM.

In this step,

add TBOM-specific roles to the SAP Solution Manager user add TBOM-specific roles to the technical user on the SUT verify the availability and correctness of the BACK destination

7.1.8 Complete

In this final step, you have to confirm the overall status of the setup for SAP TAO.

To review or change settings, choose the link in the Configuration Step column.



of 143

In case the system list remains empty:

Ensure that the correct saplogon.ini file is used by pressing the “Change System List” link andverifying the path.

Check the definition of the RFCs on the SAP Solution Manager system, using the transaction SM59 .

8.1.2 WEB

It is possible to add Web Servers as System Under Test in this view. You can also provide the system credentials ifauthentication is needed and choose language.

To add a new server in the list, press the “New” button. A window will appear to define the URL of theserver, port to be used. Description and Https protocol are the optional steps.



of 143

An existing entry can also be edited by pressing the edit button.

To delete an entry, select it and press the delete button.

Web entry definitions can be exported and then imported (on another installation for example). To do so,select the entries to export and press the export button. Then, choose where the file shall be saved. Toimport some existing definitions quickly, press the import button and select an xml file previously created bythe export feature. All definitions contained in it will be imported, if they do not already exist.

SAP Quality Center by HP8.2

The second tab of the connection module is used to define the connection towards the Quality Center server.



of 143

9 SAP TAO FunctionalitiesSAP TAO functionalities are:-

Design (Process Flow Analyzer, Inspection, UI Scanner) Run and Report Consolidation Import/ Export Change Analysis Repository investigation Self-Checks

For more information, see the application help on SAP Service Marketplace at http://service.sap.com/saptao Important Links.

You access the above mentioned functionalities via the tabs present in the left panel of SAP TAO front end.

Automating SAP GUI and Web Applications9.1

9.1.1 Automating SAP GUI application

1. Choose the Design module. .2. Click on New to add an executable.

3. Select a Type e.g. Transaction






of 143

4. Select an executable e.g. VA01.5. On the PFA tab, choose Click New . The Name for the analysis is already populated with time stamp

concatenated to it. You may change it

6. Choose Start to start the recording.7. The transaction is launched on the system under test along with the following PFA controller.



of 143

8. Execute the process flow as a business user.9. After executing the transaction completely, stop the PFA by clicking on the Stop recording button in the PFA

Control window.10. A report is generated which captures the activities performed by business user.

11. Select the analysis just created and choose Upload .The upload activity will upload components for the screens touched by user to SAP Quality Center by HP andcreate a parameterized test case. An excel sheet is created where the values entered by the user are



of 143

captured. The draft test cases will be having the library components e.g. Initialize script, launch and log onetc.

The spreadsheet will be created in the location specified in the PFA tab of configuration of SAP TestAcceleration and Optimization. The location is specified in the Data Folder field.

If the upload invalidates few consolidated components, they are shown in a pop up, and can be added to theconsolidation list.

12. Automatic generation of output parameters:

All the test script created using Process Flow Analysis functionality of SAP TAO also generates outputparameters. The output parameters can subsequently be used to create end-to-end test scripts:

Note:

Two validation components “CheckTransactionCode” and “GetMessageParameters” are added by default.The “CheckTransactionCode” validation component checks whether the transaction e.g. VA01 wassuccessfully started and “GetMessageParameters” default components en sures that the transaction wascompleted as desired.



of 143

Inserting Check Points

The process flow analysis functionality has ability to insert check points in the test cases. The end user can insertsuitable check points while recording a process flow analysis and can provide suitable conditions. The checkpointsare inserted as components in the SAP TAO generated test cases in SAP Quality Center by HP. Of course, the test failsif the check point fails.

It is possible to check the value of many properties exposed by the SAP GUI scripting APIs of a UI control and themain comparison operators are permitted by SAP TAO are:

equals (“=”)

greater or equals (“>=”)

greater (“>”)

less or equals (“<=”)

less (“<”)

different (“<>”)

When the check point is created, the value of the selected property is automatically retrieved and is set by default.

Note:

Please keep in mind that the purpose of the Checkpoint is to validate output values as they are displayed bythe application after a round-trip to the backend system. Checking input values (i.e.: values that have justbeen entered by the test engineer) does not make sense and may have a side-effect at runtime because thecheck itself will be performed before setting the value.

Inserting checkpoint using Process Flow Analysis

1. First, this functionality needs to be enabled. By default it is the case, but it can be configured through theSAP TAO configuration, in the PFA t ab with the “Add Checkpoint” radio button.

2. Start process flow analysis of any transaction.3. In the PFA Controller, click on Add Checkpoint .



of 143

4. Point the mouse to the screen element which needs validation. The selected screen element will behighlighted in red color.

5. In the PFA Controller -> Add Checkpoint, choose the property which needs validation. By default, a suitableproperty, operator and value are chosen.

9.1.2 Automating SAP CRM WebClient Application

This Section describes the procedure to automate TAO script for CRM application.

1. First go to ‘Connect’ module and select the CRM system under System Under Test(SUT)



of 143

2. Go to ‘Design’ module and Click on New butto n

3. Select Type as ‘CRM WebCient Application’ , Role and Logical link



of 143

4. Record the script by Entering required details like sales order type, Sold to party, product ID, Quantity etc. tocreate sales order and ensure that the below success message appears.

5. Upon completion of the recording, stop the recording.



of 143

6. Ensure that upon clicking on ‘Details’ of PFA at TAO, it should display the below details



of 143

9.1.3 Automating ABAP WebDynPro Application

This Section describes the procedure to automate TAO script for ABAP WebDynpro applications like SRM.

1. First go to ‘Connect’ module and select the SRM system under System Under Test(SUT)

2. Go to ‘Design’ module and Click on New button

3. Select Type as ‘Web Dynpro Application’ and click on ‘Get values from a URL’ button.



of 143

4. Enter URL and click on OK

5. The below highlighted values will get automatically filled.



of 143

6. Application will get added to the ‘design’ module. Record the script by entering required details

7. Add the checkpoints in between if required in the script



of 143

8. Stop the recording and you can see the details at TAO. Upload the PFA to QC.



of 143

9.1.4 Automating SAP Business Server pages

This Section describes the procedure to automate TAO script for SAP Business Server Pages(BSP’s).

1. First go to ‘Connect’ module and select the system under System Under Test(SUT)


3. Select Type as ‘ ABAP Web U RL’ and enter the URL in ‘Path’



of 143

4. Click on ‘New ‘button at Process Flow Analysis and record the script.

5. Do the required action on the BSP application and stop the recording



of 143

6. Check the details of PFA at TAO and upload it to QC.



of 143

9.1.5 Automating Web GUI (HTMLB) Applications

This Section describes the procedure to automate TAO script for Web GUI applications.

1. First go to ‘Connect’ module and select the system under System Under Test(SUT)


3. Select Type as ‘ABAP Web URL’ and enter the URL in ‘Path’



of 143

4. Click on ‘New ‘button at Process Flow Analysis and record the script.5. Do the required action on the Web GUI application and stop the recording



of 143

7. Check the details of PFA at TAO and upload it to QC.



of 143

9.1.6 Automating Java WebDynPro Application

This Section describes the procedure to automate TAO script for Java WebDynPro Application.

1. Go to ‘Connect’ module and select ‘web’ under SUT.

2. Click on ‘New’ Button and Enter Server, Port Details

3. Enter User name and password and click on ‘Save’ button.



of 143

4. Go to ‘Design’ module and click on ‘New’ button.

5. Enter URL as ‘nwa’ , Login Schema and click on OK button.



of 143

6. Click on New button under Process Flow Analysis. Record the PFA by entering the required values.

7. Once required actions have been performed on the application, stop recording in the PFA control



of 143

8. Check the details at TAO and upload the PFA to QC.

9.1.7 Automating SAP NetWeaver Portal

This Section describes the procedure to automate TAO script for SAP Netweaver Portal.

1. Go to ‘Connect’ module and select ‘web’ under SUT.

2. Click on ‘New’ Button and Enter Server, Port Details



of 143

3. Enter User Name and password and click on save button.



of 143

4. Go to ‘Design’ module and click on ‘New’ button.

5. Enter URL as ‘irj/portal ’ and Login Schema and click on OK button.



of 143

6. Click on New button under Process Flow Analysis. Record the PFA by entering the required values.

7. Once required actions have been performed on the application, stop recording in the PFA control



of 143

8. Check the details at TAO and upload the PFA to QC.



of 143

PFA Control Features9.2

To be able to use the new test recorder and test player capabilities, the Process Flow Analyzer control user interfacehad to be enhanced. This document explains how these new features can be used.

9.2.1 Checkpoint

Two kinds of checkpoints can be defined:

Checkpoints which really perform a check during the execution of the test and which will stop it if the checkfails.

Checkpoints which will make the value of a property of a UI element available in a further step of the test, sothat it can be reused as input for another step. This kind of checkpoint does not perform any check.

9.2.2 Define a new checkpoint

To define a checkpoint, press the Add checkpoint button.

In the tested application, select the UI element that shall be checked.



of 143

Back to the PFA control window, a new line has been added to the list of steps.

The list of properties that can be checked is automatically retrieved according to the UI element type.

If the UI element is still visible on the tested application, the value of the selected property will beautomatically filled and updated if another property is selected.



of 143

9.2.3 Checkpoint – Get Data

At this point, if the purpose of this checkpoint is just to make the UI element property value available foranother step, the type of checkpoint can be turned to ‘Get Data’. Please note that in this case, no check willbe performed.

As it is of type Get, there is no need to specify an operator and a value; this is why these fields are disabled.

For this step, a ‘GetProperty’ (or ‘GetAttribute’) default component will be inserted in the generated test. Anoutput parameter will expose the value of the selected property for the targeted UI element. Please notethat this value will also be stored in the Tao execution context.



of 143

9.2.4 Checkpoint – Check Data

If a check shall be performed, select the ‘Check Data’ option. Then, from the list of avail able operators, selectthe operator for the check to be performed.

You can then set a value for the check or let the default one, which is retrieved only if the UI control targetedby the check is still available in the tested application.

In case the tested application is updated asynchronously, select the option ‘Data Updated Asynchronously’to perform the check repeatedly until it succeeds or until a timeout is reached. This option can be used whenthe execution of the test must wait for an unknown time, for example to wait for a background job tocomplete. When this option is selected, some additional parameters can be edited.



of 143

o

Initial Wait Time: The time to wait before the first execution of the check.o Interval: The time to wait between two executions of the check.o Timeout: The total time during which checks will be performed.

The ‘Options’ field is automatically updated according to the value of these three paramete rs. This value willthen be set on the ‘Options’ parameter of the ‘CheckProperty’ default component instance which will beinserted in the generated test. Consequently, this value can also be edited manually later in the QualityCenter project.



of 143

Screenshot9.3

To make the report of the execution of a test more readable, some ‘CaptureScreen’ default componentinstances can be inserted in the test during the recording. To do so, press the ‘Add Screenshot’ button toappend the screenshot step to the recording.

Remove a step9.4

A step can be removed from the current recording. Please note that this may result in a non-executable testsince a mandatory step may be removed.



of 143

Pause9.5

It is also possible to pause a recording by pressing the ‘Pause’ and then ‘Resume’ button.

Dockable view mode9.6

The PFA control window can be reduced and docked to the top of the screen so that it takes less space onthe screen.

Test Component Generation9.7

9.7.1 Using SAP TAO Inspection

The Inspect module in the SAP Test Acceleration and Optimization client enables you to select multiple SAP GUIscreens and transactions for testing in an easy to use interface. It then determines whether these screens andtransactions are valid and uploads them as business components in SAP Quality Center by HP.

Procedure

1. Go to Design module.2. Click on New to add executable.



of 143

3. Select an executable e.g. VA01.4. Go to Inspection tab.

5. To create components and upload them to SAP Quality Center by HP, choose “Inspect”. 6. If the upload invalidates few consolidated components, then they are shown in a pop up, and can be added

to the consolidation list.7. To get the status of inspection Click “View Report”. It helps to know errors in inspection.8. If the inspection invalidates few consolidated components, then they are shown in a pop up, and can be

added to the consolidation list. This happens if the inspected component is already getting used in a testcase which is consolidated.

9.7.2 Using SAP TAO UI-Scanner

The UI Scanner enables you to collect information from one screen at a time and sends the screen objects to SAPQuality Center by HP as a component. By default, this functionality is disabled; it can be enabled from SAP TAOconfiguration. See the following screenshot:



of 143

The UI Scanner scans all objects on the screen including dynamically generated objects. The UI Scanner needs arunning QuickTest Professional (QTP) installation on system where SAP TAO is running.

Steps for UI Scanning are:-

1. Go to UI Scanner tab in the Design module

2. Click on “Launch Scanner”.Ensure that only one SAPGUI session is running for your system under test.



of 143

3. Choose .

4. To end the scan, choose .The UI screen will be scanned and will be uploaded to components module of SAP Quality Center by HP. Itwould reside in the folder SAP Front End\Transactions\<T Code>.

5. If the UI-Scanning invalidates few consolidated components, then they are shown in a pop up, and can beadded to the consolidation list. This happens if the re-UI Scanning is done for a component which is alreadygetting used in a test case which is consolidated.

Test execution in SAP TAO Run and Report9.8The Run and Report module of SAP TAO allows executions of both single tests and multiple tests as combined intoSAP TAO run-lists.

9.8.1 Displaying Run and Report-relevant DataIn the Run and Report module of SAP TAO, you can display the following data:

To access the data table belonging to a test, do the following:

1. Select a test.

2. Click on the Initial Data Table link.

To see the initial system and the initial executable object, refer to the top of the UI.

To access SAP TAO-based logs, choose the Reports view.

Execution reports are generated by the SAP TAO RTL at runtime, reporting the details for each execution stepof the test. However, the final test execution result is given in the end by SAP Quality Center by HP .Therefore, it may differ from the status of the TAO report if, for example, connectivity errors between QC andQTP appear, which SAP TAO is not aware of, or if a failing error handling in the CBASE does not catch the lasterror.



of 143

9.8.2 Adapting SAP TAO Run List SettingsA run list is an entity in SAP TAO which allows combining multiple single tests into one execution list.

You have the following options:

When saving a run list, a corresponding test set is created in SAP Quality Center by HP. You can adapt thedefault location and prefix which is displayed in the “Save Runlist” dialogbox.

You can also execute a run list without having it saved before. In this case a test set is implicitly created in SAPQuality Center by HP, according to the location and the naming prefix in SAP TAO configuration.

Note:

When executing a test entity in SAP TAO Run and Report, technically a test set is created and executed in

SAP Quality Center by HP.

The default values for the test set folder and the naming prefixes can be set in SAP TAO Configuration at the Run &Report tab page:

A previously saved run list can be reopened for execution and further modification from within the " Run List" tab page in SAP TAO Run and Report.



of 143

To re-arrange the test case execution sequence, use the up and down arrows.

9.8.3 Pausing a run listTo request a run list to be paused, choose Pause .

SAP TAO applies the pause at the next logical point. If the user presses Pause during the execution of a testcase, the run list is paused after the execution of the current test case is finished.

TBOM creation in SAP TAO Run and Report9.9The following sub-chapters lead you to TBOM creation by SAP TAO:

We explain

How to set and verify the generic system configuration

How to verify the project-related configuration

How to use the TBOM creation functionality

9.9.1 Basic configuration for TBOM creation by TAO

9.9.1.1 Checking User IDs and Authorizations To re-use SAP TAO-based test cases to create TBOMs, several authorizations are required on SAP Solution Managerand system under test.

Possible User ID combinations:

User in SAP SolutionManager

User in system under test User passed to Launch andLogin component of a testcase (present in dataspreadsheet)



of 143

Case 1 In SAP TAO configuration:“User ID A”

Configured in SAP TAOconnection: “ User ID A”

Test execution with “UserID A”

Case 2 In SAP TAO configuration:“User ID A”

“User ID A“ exists (but it isnot used for execution)

Configured in SAP TAOconnection: “User ID B”

Test execution with “UserID B”

Depending on the User/ID combination, the following authorizations are needed:

Case 1:

User A needs the following authorizations on SAP Solution Manager

Required role to display Business Blueprint Structure of a solution manager project:SAP_SOL_PROJ_ADMIN_DIS

Required role to create / modify TBOMsSAP_SM_BPCA_TBOM_ALL

Required role to start/ stop trace recording on the managed SAP system, and to subsequently collectthe trace information for TBOM creation:SAP_S_RFCACL

User A needs at least the following authorizations on the managed SAP system

Required role to be able to start/ stop trace recording on the managed SAP system, and tosubsequently collect the trace information for TBOM creation:SAP_S_RFCACL

User A is authorized to process business transaction on the system under test.

Case 2:User A needs the following authorizations on SAP Solution Manager

Required role to display Business Blueprint Structure of a solution manager project:SAP_SOL_PROJ_ADMIN_DIS

Required role to create / modify TBOMsSAP_SM_BPCA_TBOM_ALL

Required role to start/ stop trace recording on the managed SAP system, and to subsequently collectthe trace information for TBOM creation:SAP_S_RFCACL

User A needs at least the following authorizations on the managed SAP system

Required role to be able to start/ stop trace recording on the managed SAP system, and tosubsequently collect the trace information for TBOM creation:

SAP_S_RFCACL

User B needs to have at least the following authorization on the system under test

User B is able to process business transaction on the system under test.



of 143

Caution

Authorizations for executing the business scenario(s)

In case 1: User A is authorized to process the business scenario(s)

In case 2: User B is authorized to process the business scenario(s).

(Note: User B does not need to have RFC authorizations)

9.9.1.2 Checking the Existence of Trusted RFC ConnectionsThis chapter describes how to verify that the required trusted destinations are present on your installation. Thesystem administrator can create the needed connections and RFC destinations in the SAP Solution ManagerConfiguration work center for the system under test (Transaction SOLMAN_SETUP -> System under TestConfiguration -> see amongst others "Connect System under Test").

For TBOM creation, a trusted RFC connection must be available in both directions between the SAP SolutionManager and the system under tests. This is necessary for switching on/off the traces which are required for thispurpose. As described in the following chapters, this is an important step. Note additional steps are also required forTBOM creation.

1. To verify the existence of an appropriate trusted RFC connection, Go to transaction SM59 and choose theABAP concerned destination. A screen like the following one appears:



of 143

2. On the Logon & Security tab page, ensure the configured user matches with the user provided in SAP TAO forthe SAP Solution Manager connection. Typically the configured user is the current user, so any user specifiedin SAP TAO for SAP Solution Manager connection is valid.

3. Execute the Remote Logon to log on to the corresponding system under test.

4. In the system under test ensure both Back and Trusted connections are present:

5. From the system under test try to logon to SAP Solution Manager using this trusted RFC connection.

6. In transaction SM59, open the *BACK destination and execute both the Connection Test and the AuthorizationTest available in the Utilities menu.

9.9.1.3 Providing the Message Server Host Via SAP Logon EntryThe entry for the system under test in SAP Logon must appropriately provide the message server host as this isneeded to determine the actual system under test.

To create the entries for the system under test, you can configure the following:

the message server host

or

the application server host.

Exemplary screen-shots for either load balanced or direct application server:

Exemplary screen-shot showing 4 valid entries in SAP Logon and 1 invalid entry (the INVALID one is outlined in blue):

Background: The message server host together with the short SID allows composing a unique key for determining

the target ABAP system. SAP TAO will first use the “Message Server” property, but if it is not provided, it uses the“Group/Server” entry. The fall back to “Group/Server” works only if the application server and message server areon the same host.



of 143

9.9.1.4 Enabling TBOM in the SAP TAO ClientThe TBOM creation functionality must be explicitly enabled.

To do so, under Configuration choose the Run & Report tab page.

To improve SAP TAO performance, ensure the TBOM creation functionality is switched off if it’s not required.

9.9.2 Project specific configuration for TBOM creation by TAO

9.9.2.1 Preparing the SAP Solution Manager Project

Configuration check scenario

To verify the settings in a simple but real scenario, it is recommended to do the following check:1. In your Solution Manager project, select an executable item2. Press the ‘Attributes’ button.

The attributes popup opens. Go to the ‘TBOM’ tab. 3. Create manually a dynamic TBOM by pressing the ‘Record TBOM’ button.

This should automatically log you into the system under test and start the transaction of the executableitem. If automatically log on is not happening it means trusted RFC connection is missing and it should be

created. 4. Run a small business process example and confirm the TBOM creation at its end.5. Verify that a TBOM entry has actually been created on Solution Manager System.



of 143

If the ‘configuration check scenario’ did not successfully create a TBOM, you need to solve this problemfirst. SAP TAO won’t be able to create TBOM either.



of 143

The following check should be done if manual TBOM creation from SAP TAO fails:

Check 1 - Existence of appropriate executable item in Solution Manager Project

1. Ensure that on your SAP Solution Manager an appropriate business blueprint structure exists and that itcontains the executable item(s) for which you want to create the TBOM(s).

2. Log on to your Solution Manager using the same user ID as you use in SAP TAO (set in “configuration – licensing” in the SAP TAO client). Open the SAP Solution Manager project you intend to process (transactionSOLAR01) in order to view the ‘Logical Component’ and it’s ‘System Role‘.

In the above given screen-sho t, the configured logical component is ‘Z_QB2_SMY’ and the user -specific system roleis ‘Quality Assurance System’.

Check 2 - Verify validity of Logical Component

The following is describes how to verify that the executable item is configured correctly to allow TBOM creation by

SAP TAO.Note that this verification is only necessary once for a set of attributes “SolMan User ID / SolMan project/ logical component”.

1. Verify in SMSY that the executable item contains the product system which points to the physical systemwhere later on the test shall be executed. If more than one product system is configured in the logicalcomponent, the user- specific ‘system role’ will be used to determine the target product system. In the presentexample the system role is set to be “Quality Assurance System”, thus SAP TAO will use the highlighted entryof the Logical component Z_QB2_SMY:

HintIf there is exactly one product system assigned to the Logical Component, SAP TAO uses that system without regardsto the active system role.



of 143

2. Double-click on the highlighted entry to navigate to a table showing the system landscape.

3. Select the entry containing the ‘relevant ECC’ server and its configured RFC destinations will be shown.In the context of TBOM creation we are interested in the “Trusted System RFC” which you already haveverified before.

9.9.3 Actually creating a TBOM with SAP TAOThis chapter explains how to actually create a TBOM with SAP TAO.

Prerequisites

You have performed the previously described configuration.

You have access to a process step with an appropriate executable item in the target SAP Solution Managerproject.

9.9.3.1 Associating a TestSAP TAO-based test cases can be reused to create TBOMs. TBOMs are created in SAP Solution Manager, and can beviewed in Business Blueprint (SOLAR01). To define where a test case shall create / update TBOM later-on, a linkbetween the test case and the business blueprint executable mu st be established, a so called “association forTBOM”.

You need to take care that you choose a test case which represents the typical user activity on the executable. Therisk for an invalid mapping is that if you associate a test case which does not represent the appropriate scenario,then the TBOM will not contain the right objects.

Procedure

1. Identify the appropriate test case which is to be associated to the business blueprint executable.

2. Open SAP TAO.

3. Choose Run & Report .

4. Select the test case

5. Click on the icon in the Tests tab, or select the entry ‘Associate for TBOM creation’ of the context menuof the test. The association popup will open.

6. Select the SAP Solution Manager project which contains the executable item to which the association shall bemade.



of 143

7. Select the executable item. In case of huge projects it is recommended to activate the ‘Filter on Object Name’in order to ease the finding of the right executable. Select the de sired executable and press the “Associate” button in order to create the association.

Note that in order to become ‘executable for TBOM creation’, several conditions must be met where theexistence of an association is only one of them. For example, it is possible to establish an association withoutbeing connected to any system under test, but in order to become executable, the connection to the appropriatesystem under test is mandatory.

9.9.3.2 Executing the Associated Test

Once all conditions which make a test case executable for TBOM creation are met the corresponding the menubutton and its context menu entry of the test case become activated.

The following options for creation/update of TBOM do exist:



of 143

The test case can be executed manually, for this select the test at the Tests tab of Run and Report module and

click on . Note that this is also possible via the context menu associated to the test.

The test case can be added to a run-list which allows the execution of multiple test cases in one run. You caneither add tests one by one to a run list, or you can select complete folders.

a. Select the tests/ folders you are interested in and click on .

b. Switch to the ‘Run List’ tab, select the tests you want to execute and select their ‘Create TBOM’ checkboxes boxes in order to request TBOM creation during the test execution.

c. Press in order to execute.

Notes:

If a dynamic TBOM created by the same test case in a former run already exists, the re-execution of thesame test case will update the existing TBOM.

If a dynamic TBOM exist, but it was NOT created by the same test case by SAP TAO TBOM functionality, thenthe ‘Execution for TBOM creation’ creates a TBOM enhancement. Those enhancements are not visible bydefault in the main TBOM tab (see FAQ for hints).

To be able to follow detailed information about the TBOM creation progress, it is recommended to activatethe Information Display via SAP TAO Configuration → Log → “Options: Display Information Box”.

Higher level test cases (e.g. O2C test case) cannot be used to create TBOM for lower level process steps (e.g.VA01 Create Sales Order). A SAP TAO-based test case is needed for each executable item.

Consolidating Tests9.10Consolidation has two benefits:-

It makes a test case better for execution, so it becomes faster.

It creates a component out of a test case, so that it could be used to compose other test case.



of 143

Important configurations for Consolidation

Automatic update of data table: This will automatically update the Excel data file with new column name if afield, which is not present in the Excel data file, is found.

Creation of test case which will use this component: This helps in the execution of a test case.

Consolidation can be initiated by:

Select by Test Tab

Select by Component Tab

9.10.1 Select by TestIn the C onsolidate module go to “Select by Test” tab. If SAP Test Acceleration and Optimization is not connected toSAP Quality Center by HP, then user would be forced to connect to use this functionality. Once connected, you canview the folder structure of the component module of SAP Quality Center by HP.

9.10.1.1 Consolidating a test

Select a test and click on “Add to Consolidation list”. By default, all the child test cases are added toconsolidation list.

Example: If VA01 Consolidated component is used in O2C Test Case, and O2C is again consolidated, then ifVA01 test case is added to consolidation list with “Add Dependent Tests” checked, even O2C Test Casewould be added to the consolidation list.

9.10.1.2 Invalidating test casesYou can select multiple test cases, and click on the button “Invalidate”, and mark all the dependent test

cases for consolidation. The pop up shows the entire dependent test cases, and could be added directly forconsolidation.

This feature is beneficial if test cases are changed in quality center.



of 143

Example: If VA01 Consolidated component is used in O2C Test Case, and O2C is again consolidated, then ifVA01 test case is manually invalidated, even O2C Test Case would be marked for consolidation.

9.10.1.3 Identifying Dependent TestsTo display all test cases making use of the test cases of the consolidate component, select a test case andclick on the button “Identify Dependent Tests”.

Example: VA01 consolidated component is used in O2C Test Case and O2C is again consolidated. If VA01 isselected and “identify dependent tests” button is pressed, a pop up window appears to show the dependenttest cases, which are VA01 and O2C. These test cases could also be added for consolidation directly from the

pop up.

9.10.1.4 Updating IterationsThe functionality enable the SAP TAO generated test cases to run for all rows entered in the associated data

table Excel sheet.



of 143

9.10.1.5 Updating the Data TableThis functionality compares the fields referenced in the data table with the ones mentioned in the selectedtest case. If the test case has more fields, the additional fields are added to the data table.



of 143

In the above example, a field was parameterized in the test case but it does not exist in the data table

reference of the test case. When (re)consolidating the test, DT_VA01_0101_DIVISION is added as a columnin the data table.

9.10.2 Select by Component1. In the Consolidate module go to “Select by Component” tab.

You see the components present in the components module of SAP Quality Center by HP.

2. Select a component.You see the tests using this component.

3. Select one or more tests, and choose “Consolidate”.



of 143

Using Change Analyzer9.11Change Analyzer functionality helps to repair tests impacted by a software change. SAP Test Acceleration andOptimization uses the SAP Solution Manager – Business Process Change Analyzer (BPCA) result. The BPCA result IDcan be searched on the basis of a solution or SAP Solution Manager project.



of 143

Steps for Change Analysis:-

1. Enter your result ID, and choose “Change Impact Analysis“.

The List of impacted components (including consolidated components) is shown in the Impacted Componentstab. Impacted Test tab shows are all the affected tests.

2. Select the impacted components and choose “Repair”. If basic components are selected, the repair task is re-inspection. If a consolidated component is selected, therepair task is reconsolidation.Once the repair is over, the components are flagged “Repaired“. Even without performing the reparation task, acomponent could be flagged repaired using context menu.



of 143

SAP TAO Repository9.12Repository module gives access to SAP TAO repository stored in SAP Solution Manager.

9.12.1 Displaying ComponentsYou can display all components you created for a specified QC Domain and QC Project.

9.12.2 Displaying PFA RecordingsYou can search for PFA recording, depending on search strings. You can specify the property to search on. Thedifferent properties which are possible to be searched on are the following:

User

Analysis Name

Transaction



of 143

System

Client

Date Time

Language

Once the search is done the user can click on one of the PFA to see more technical details.

9.12.3 Repository SynchronizationThis functionality helps in synchronizing the SAP TAO data base with SAP Quality Center by HP component data base.

9.12.3.1 Enabling Repository Synchronization1. Choose Configuration → Import/Export.

2. Select the Show Repository Synchronization Tool checkbox.



of 143

9.12.3.2 Performing Repository SynchronizationProcedure

1. Click on "Get Data“.

Missing and orphan components are displayed. Missing Components: Missing components are the components which are present in SAP Quality

Center by HP but not present in SAP TAO repository. These components need to be replicated in SAPTAO data base as well.

Orphan Components: These components are present in SAP TAO data base, and not in SAP QualityCenter by HP. These component needs to be deleted from SAP TAO database as well.

2. To display the missing data in the table, choose the Propose Missing Data button.

3. To edit the missing data, click on the Edit Button.



of 143

4. Select the multiple missing components and click on the repair button.The missing components are replicated into the SAP TAO data base.

5. Select multiple orphan components and click on Repair button.The orphan component(s) is/are deleted from SAP TAO data base.



of 143

Identifying Properties of UI Elements Using Object Spy9.13Object Spy is used to learn the properties of UI elements on the screen.

Procedure

1. Launch the SAPTAO Application.

2. Launch Sap Logon, connect to a SAP system with scripting enabled, enter user/password and launch atransaction.

3. In SAP TAO, click on the link labeled "Object Spy" in the upper right corner. The object spy dialog shouldappear.

In the object spy dialog, all existing Sap Gui sessions, with scripting enabled, are listed in the dropdown listlocated in the "Active connections" group box: the system, transaction and user should be displayed justbelow this list. The program name and the screen number of the selected session should also be displayed inthe "Session info" group box.

A preview picture of the selected Sap Gui session is displayed in the "Active connections" group box.

4. Press the button labeled "Spy" in the bottom area and go back to the SAP Gui window.

5. Move the mouse over the SAP Gui window. Controls located under the mouse should be highlighted in red.Click on one control and the highlight mode should stop.

6. Go back to the object spy window. All the properties of the selected control should be listed at the bottom.



of 143



of 143

7. To locate the targeted SAP GUI control and to display the list of its related RTL components, right-click on a spyresult.



of 143

All RTL components delivered with Sap Tao SP4 and related to a specified SAP GUI control type are listed inthis view.

For ALV controls, the identifiers of its sub-items are displayed in sub-nodes, for example, here in the ALVtoolbar, the menu- item “Project”, of the button -menu which has the tooltip “Create”, has the identifier“CREATE_PRJ_NEW”.



of 143

9.13.1 Spying an ALV controlThe ABAP List Viewer (ALV) is a generic tool that can be used to output data in tabular form and is increasingly usedby the applications particularly as of Release 4.6C of Sap GUI. By using the ALV, general functions are provided (forexample, exporting to Excel) and it is possible to adapt the output to customized requirements (for example, sorting,filters, totals calculation). There are different types of ALV, for example trees, grids, etc.

Since SAP TAO SP2, it is possible to spy a particular object inside an ALV control, for example a single node of an ALVtree.

Note:

It is essential to keep all spaces and special characters when copying something from the column ‘Value’. Allvalues are displayed exactly as they have to be passed to a default component.

SAP TAO Log9.14Each time SAP TAO-based scripts are executed, SAP TAO logs are created in the SAP TAO Runtime Library Folder,

E.g.: If SAP TAO RTL Folder is C:\SAPTAORTL, then logs are kept in C:\SAPTAORTL\Logs.



of 143

9.14.1 Accessing Logs From SAP TAO Frontend

SAP TAO provides a new module Run and Report which enables you to execute SAP TAO scripts andalso view SAP TAO logs. Wherever the test has been executed from, via Test Lab module of SAP Quality Center by HPor using SAP TAO, the logs can be viewed in SAP TAO frontend.

Steps to access logs for a test case execution:

1. Select a test case.

2. Select a specific test set

3. View the executions logs.



of 143

4. You have the following options:

Arrange the columns and see only specific steps.

Save the change in the view.

To access the SAP TAO xml log file, click on HTML report.



of 143

9.14.2 Accessing SAP TAO logs (log xml file)To access the logs xml file and find the logs for an execution run, you go to the specified log folder. You can alsonavigate to the specified folder by going through run and report module or using the Report folder link.

If you have executed a business process test from the Test Plan module, a folder “ BusinessProcess_YYYY-MM-DD_HH-MM-SS_Test Case Name” is created . The time stamp of the start of the execution of business process isappended in the name of the log folder.

In this folder, open the file ReportLog.xml in Web Browser. The content of the entire log file is displayed. The log fileis an xml file on which the log.xslt style sheet is applied.

For a test set run from test lab module, a folder with “ TestSet_Test Set name” is created in the log folder of RTLfolder.

For a business component run from QTP, a folder with “ BusinessComponent_ YYYY-MM-DD_HH-MM-SS_TestComponent Name” is created in the Log folder of RTL folder.



of 143

10 Example for Test Case CreationIn this example, you learn how to create a composite script, where we link Create Sales Order and View Sales Order.This example demonstrates how to pass parameters from one script to another.

The following steps are described:

1. Test case creation for Create Sales Order

2. Test case creation for View Sales Order

3. Creation of composite test case, which links Create Sales Order and View Sales Order test cases

Test Case Creation for “Create Sale Order” 10.1

10.1.1 Performing a Process Flow Analysis for Create Sales Order Transaction(VA01)

In this example, we will use the process flow analysis functionality of SAP Test Acceleration and Optimization torecord a transaction. This functionality records the execution flow and stores the recorded information in arepository which resides in SAP Solution Manager.

1. Choose (“Design ”) in SAP Test Acceleration and Optimization client. 2. Choose the “New ” pushbutton in the transaction list screen area.3. Enter the transaction code VA01 .4. Choose “ OK”. 5. In the “ Executable Objects ” screen area, select the transaction VA01 .6. Click on “New ” in Process Flow Analysis tab; enter the name as Create Sales Order. 7. Choose “ Start ”.



of 143

The “PFA Control” window appears.



of 143

The transaction VA01 is started and initial screen is shown.8. Enter the following data in the initial screen,

“Order Type ”: OR “Sale Organization ”: 1000 “Distribution Channel ”: 10 “Division ”: 00

9. Press “ Enter ” 10. In the second screen, enter the following data:

a. “Sold-To Party ”: 1000 b. “Ship-To Party ”: 1000 c. “Material ”:p -100d. “Quantity ”:1

11. Choose “Save”

12. In the “ PFA Control ” window, choose “ Stop recording ”.



of 143

13. In SAP Test Acceleration and Optimization client, select “ Create Sales Order ” in the existing analysis. 14. Choose “ Details ”.



of 143

15. Note down the sales order number shown in the report, which will be used in the exercise 2.16. Close the “Process Flow Analyzer Report” window by clicking on the “ Close ” butt on.

10.1.2 Uploading the Process Flow Analysis of Create Sales Order Transaction

(VA01)1. Select “ Create Sales Order ” in the “ Process Flow Analysis” tab.



of 143

2. Choose “ Upload ”.3. In the “ SAP TAO” dialog box, choose “Yes”.

4. Once the upload is done, view the upload report by clicking on a link near the uploadstatus bar.

Note that the screen components are inspected for the test system (ERP) and are uploaded to SAP QualityCenter by HP.

5. Close the “ Process Flow Analyzer Upload Status ” report window by choosing “ Close ”. 6. On the top right corner of SAP TAO client, click on “ SAP Quality Center ”.

The SAP Quality Center by HP will get launched in the Microsoft Internet Explorer web browser.

7. Provide the login credentials in the SAP Quality Center by HP login.



of 143

8. Navigate to the test plan module by clicking on in SAP Quality Center by HP.

9. Choose “ Design ” folder.

10. In the “ Design ” folder, choose “ Create Sale Order ” test case.



of 143

11. To open the data file, navigate to location specified in “ DataTablePath ” field of InitilizeContext. The path

would be

Alternatively, you can also navigate to the data file from Run and Report module of SAP TAO. 12. Select the

test and click on .



of 143

10.1.3 Storing the Sales Order Number in the Data Table Excel Sheet

1. Drag and drop the GetMessageParameter component in the suitable location of the test case. Generally, itwould be dragged and dropped before the automatically added GetMessageParameters component.

2. Provide the same URI of GetMessageParamters component to the GetMessageParameter component. Usethe suitable index for storing the value. You find this index by using QTP object spy. The index in the case ofstandard VA01 transaction is 1.TargetField is the DT_XXX which is a column name in the data table Excelsheet.

10.1.4 Adding Manual Validation on the Status Bar

1. While recording the PFA use the ‘Add Checkp oint’ functionality to inject the CheckProperty component forstatus bar validation.

2. After the PFA upload, the check property component is introduced after the ‘GetMessageParameter’component.

3. Modify the data table Excel sheet to capture suitable string for validation.

The context parameter %VA01_MessageParameter1% can be noted from the PFA Details tab which showsthe structure.



of 143

10.1.5 Consolidation of the Create Sales Order Test Case

Introduction to Consolidation : This activity in SAP Test Acceleration and Optimization creates a component out of atest case, which has following benefits:

It makes a test case better for execution, so it becomes faster. It creates a component out of a test case, so that it could be used to compose other test cases.

The steps for consolidation are:

1. Choose in SAP Test Acceleration and Optimization client.2. In the “ Select by Test ” tab page, choose “ Subject ”->”Design ”->”Create Sales Order ”.

3. Choose .4. Click on the “ Consolidation List ” tab page. Ensure that the “Create Sale Order” test case is selected.



of 143

5. Choose .

6. Once the consolidation is complete, check the status of consolidation by clicking on .

10.1.6 Executing the Create Sales Order Test Case and Viewing HP QuickTest

Professional Execution Logs

1. Navigate to Test Lab module of SAP Quality Center by HP by clicking on .

2. Create a folder by clicking on .



of 143

3. Enter “ Folder Name :” Tech Ed 2010.

4. Create a new test set in the folder “ Tech Ed 2010 ” by choosing .

5. Double click on the “ Create Sales Order ” test set.

6. In the “ Execution Grid ” tab page, choose .7. Select the “ Test_Create Sales Order ” test case from the “ Consolidated ” folder. 8. Add this test case to the execution grid by double clicking on it.

9. Select the row with “ Test _Create Sales Order ” in the execution grid.



of 143

10. Choose .

“Automatic Runner ” window will appear.

11. Select the “ Run All Tests Locally ” checkbox and keep the “Enable Log” checked.

12. Choose .

The execution of Create Sales Order (VA01) transaction starts after some time. The VA01 transaction isexecuted as recorded. The status of “Test_Create Sales Order” test case changes to “Passed”.

13. Close this window.The status of “ Test_Create Sales Order ” test case changes to “Passed” in Execution Grid as well.

14. To view the HP QuickTest Professional Logs, double click on “ Test_Create Sales Order ” row. 15. In the “ Test Instance Properties ” window, double click on the first row.16. In the same window, double click on the link .



of 143

The HP QuickTest Professional by HP log appears.



of 143

10.1.7 Viewing SAP TAO LogsNavigate to Run and Report module of SAP TAO and select the test case Test_Create Sales Order.

Select a latest test set, and see the SAP TAO logs.

Test Case C reation for “View Sales Order” 10.2

10.2.1 Performing Process Flow Analysis of the “View Sales Order” Transaction

(VA03)

1. Choose (“Design ”) in SAP Test Acceleration and Optimization client. 2. Choose the “New ” pushbutton in the transaction list screen area.3. Enter the transaction code VA03 .4. Choose “ OK”. 5. In the “ Executable Objects ” screen area, select the transaction VA03 .6. Click on “New ” in Process Flow Analysis tab; enter the name as View Sales Order.



of 143

7. Enter the sales order number generated in recording of “Create Sales Order”.8. Choose “ Search ”.

9. In the “ PFA Control ” window, choose “ Stop Recording ”.



of 143

10. In SAP Test Acceleration and Optimization client, select “ View Sales Order ” in the existing analysis.11. Choose “ Details ”.12. Close the window after verifying the structure.

10.2.2 Uploading the Process Flow Analysis of “View Sales Order” Transaction(VA03)

1. Select the “ View Sales Order ” in the existing analysis box. 2. Choose “ Upload ”.

A pop up box will appear to confirm the upload.3. Choose “ Yes”.

4. Once the upload is done, view the upload report by clicking on a link near the uploadstatus bar. Notice that the screen components are inspected for the Test System (ERP) and are uploaded toSAP Quality Center by HP.

10.2.3 Consolidating the Create “View Sales Order” Test Case

1. Choose in SAP Test Acceleration and Optimization client.



of 143

2. In the “ Select by Test ” tab page, choose “ Subject ”->”Design ”->”View Sales Order ”.

3. Choose .4. Select tab page “Consolidation List”.5. Check that “View Sales Order” test case is selected.

6. Choose

Once if the consolidation is complete, check the status of consolidation by clicking on .

Creation of a End-to-End Test Case10.3

10.3.1 Creating a End-to-End Business Process Test Case and use Single Data file

10.3.1.1 Creating a Composite Business Process Test Case

1. Navigate to the test plan module by clicking on in SAP Quality Center by HP.2. Choose “ Subject ”->”Design ” 3. Using the secondary mouse button, choose “ New Test ”.

4. Select “ Business-Process ” as the “ Test Type ”.

5. Enter “ O2C” as the test name and choose ok. Click on “Test Scripts” tab. In the components tab, select“Create Sales order” test case and choose . Then select “View sales order” and choose .



of 143

6. Go to O2C and now the script at Test plan looks like below

7. Click on “Iterations” for the “View Sales Order” and change ‘C1_InitializeContext_TestOptions’ parametervalue to ‘/c’

Note:

‘/c’ option is used to report all the values in a single TAO log file. If more than one script is used in acomposite test case then from second script onwards , this option has to be changed to ‘/c’

8. Create one data file and name it as ‘DT_O2C’ and copy paste the values from individual data files (DT_CreateSales Order, DT_View Sales Order). Ensure that the below parameters are copied only once to the data file.



of 143

9. Output of one script is input to another script and this can be achieved through data file

Option1:

In the DT_O2C.xls, enter %VA01_MessageParameter1% in the column DT_VA03_0102_ORDER . Theinformation on the parameter name could be capture by checking the structure of “Create Sales Order”process flow analysis.

Option2:

In the DT_O2C.xls, give reference to the column DT_VA03_0102_ORDER form the columnDT_VA01_SALES_ORDER (This is the column where the order is captured).



of 143

10.3.1.2 Consolidating an End-to-End Test

1. Click on the icon in SAP Test Acceleration and Optimization client.2. In the “ Select by Test ” tab page, choose “ Subject ”->”Design ”->”O2C”.

3. Choose .4. Choose “ Consolidation List ” tab page.

5. Ensure that the “ O2C” test case is selected.

6. Choose .

10.3.1.3 Executing and End-to-End test and Viewing HP QuickTest Professional Logs

1. Navigate to Test Lab module of SAP Quality Center by HP by clicking on .2. Navigate to the folder “ Tech Ed 2010 ”.

3. Create a new Test Set in the folder “Tech Ed 2010” by clicking on . Give the name of the test set “O2C” 4. Double click on the “O2C” test set. 5. In the “ Execution Grid ” tab page, click on “ Select Tests ” button. 6. Select the “ Test_O2C ” test case from the “ Consolidated ” folder.7. Add this test case to the execution grid by double clicking on it.



of 143

8. Select the row with “ Test _O2C ” in the execution grid.

9. Choose .

The “ Automatic Runner ” window appears.

10. Select “ Run All Tests Locally ” and keep the “ Enable Log ” checked. 11. Choose

The execution of O2C scenario takes some time to start. The O2C Scenario is executed. The status of“Test_O2C” test case change s to “ Passed ”.

12. Close the “ Automatic Runner ” window.



of 143

13. In the “ Execution Grid ” tab page, double click on the first row.

14. In the “ Test Instance Properties ” window, double click on the first row.15. In the same window, double click on the link at the bottom.

The HP QuickTest Professional by HP Log appears. The SAP TAO logs can be accessed via SAP TAO Run andReport module.



of 143

10.3.2 Creating an End-to-End Test Case and use Multiple Data files

1. Repeat the steps from 1 to 7 in 11.3.1.1 section2. Output of one script is input to another script and this can be achieved through data file

Option1: Open the DT_View Sales Order.xls file and enter %VA01_MessageParameter1% in the columnDT_VA03_0102_ORDER . The information on the parameter name could be capture by checkingthe structure of “Create Sales Order” process flow analysis.

Option2:

i. Pass the Value from one data file to another data file by using “Transfer Data” component.This is a default component



of 143

ii. Transfer component has to be used in between the 2 scripts

iii. Values have to be mentioned in the Transfer component

iv. Now sales order number will get copied from “DT_Create Sales Order.xls” to “DT_View SalesOrder.xls”

3. Repeat the steps in section 11.3.1.2 for consolidation and execution



of 143

11 Repairing SAP TAO Test Cases

Introduction to Different Change Types11.1Lot of times SAP TAO-based test cases would not run successfully, as they are damaged due to software changesintroduced in the landscape. The following section explains how SAP TAO-based test cases can be repaired easily.

Following are the 2 kinds of changes which may damage test cases:

1. Custom code change : Such kind of changes may introduce new mandatory fields or make the existing fieldmandatory for the user, hence the corresponding test case should be repaired to handle the change. If a newmandatory field is introduced in the screen, then its corresponding screen component needs to be re-created (re-inspected), so that a new parameter is introduced in the test component. If an existing field hasbecome mandatory, recreation of the component is not required as it’s already present in the correspondingscreen component. Later, the test cases should be tuned to handle the new parameter.

2. Customizing change: Such kind of change may also introduce new mandatory fields or make the existingfield mandatory. In such situation, re-creation of the test components is not required, as by default SAP TAO

always creates a component which has all possible fields. Only, the test cases should be tuned to handle thenew parameter.

Example of SAP TAO screen component: The screen component for 101 screen of VA01 transaction alwayshas many parameters in the component consisting even those which are not always shown on the screen.The following screenshots show a standard 101 screen and its inspected component.

We note that 101 screen shown to a user has 7 input fields while the inspected component has 9 parameters. Thecomponent is created considering all possible fields, so in many cases of customizing change re-inspection of screencomponents is not required.

The following graphic explains the general repair process of SAP TAO-based test cases. Later, we see how differenttypes of changes can be managed to repair the affected test cases.



of 143

Repairing Test Cases Due to Customizing Changes11.2Customizing change is very common change in SAP Landscape, and it alters the way a user interacts with a system.Lot of times existing fields become mandatory or new fields are introduced in the existing flow of a transaction.Sometimes, changes are too drastic where new screens are introduced in the existing flow. If the identified changes

are too drastic and create different test flows, it’s recommended to create a new test case using Process FlowAnalysis.

The repair of test cases could be handled in the following ways depending on whether BPCA functionality is used ornot:

1. Repair without BPCA integrationIf you do not meet the prerequisite for using BPCA, repair the SAP TAO-based automated test case by thefollowing approach:1. Identify impacted test cases – The test cases impacted due to software changes have to be manually

identified. The test engineer can seek this information from the introducer of the change or he may runimportant regression test cases to identify the impacted ones.

2. Execute the test cases – The test case needs to be executed once to check whether it’s really failing. If atest case execution fails, the test engineer notes down the new input required. It might have happened

Identify Impactedtest cases

Execute impactedtest case to know

if it fails andwhere

Repair testcomponets

Repair test cases

Consolidate testcases

Provide input datain data excel

Execute repairedtest cases

The suitable data is provided for each parameter value(new mandatory field) in the date file.

Execution of a test case is needed to check the repairactivity.

Consolidation of a test case helps in passing on thechanges to higher level test cases.

The test component which is impacted due to softwarechanges needs to be repaired if new UI fields have beenadded. The repair of test component can be done byusing inspection or Change Analyzer module of SAP TAO.

Test case can be repaired in many ways, e.g. injecting anew component, parameterization of new field, etc.

The identified impacted test cases are executed once toknow whether test cases fail. In case a test fails, refer to

the execution help to figure out the reason (e.g. changeof underlying software component).

Identification of impacted test cases could be manual orautomatic using Business Process Change Analyzerfunctionality of SAP Solution Manager



of 143

that an existing field on the screen has become mandatory or a new field has been introduced. Theexecution of the test case can also be done from SAP TAO’s Run and Report module.

3. Repair the test cases – Now the test case needs to be modified to handle the input found in the step 2. Asuitable parameter value should be provided for the field in the identified test case.

Note:

To accurately identify the screen component needed for feeding this new value, the test engineer may needto check the technical information of the screen in the transaction. This way, he could accurately identify thescreen number. If the equivalent component for the screen number is not present in the BPT module of SAPQuality Center by HP, it can be generated by the SAP TAO Inspection functionality.

4. Consolidate the test cases - The test cases which were modified need to be consolidated, so that all the

higher level test case can get the fixed component. The consolidation automatically adds one extracolumn in data table Excel sheet for the new parameter value, e.g. DT_XXXX_XXXX.5. Provide input data in data table Excel sheet – The test engineer needs to provide suitable data in the

data table Excel sheet for the mandatory input field.6. Execute the repaired test case – The repaired test case needs to be executed once to check the fix done

to handle this new input.

2. Repair using BPCA Integration1. Identify impacted test cases – The impacted test cases can be easily identified in SAP TAO using its

Change Analyzer module. In this module, you provide the BPCA ID, which is generated in SAP Solution

Manager. The ID could also be easily searched.2. Execute the test cases – You can run the impacted test cases from SAP TAO itself, and you do not need

to navigate to SAP Quality Center by HP to execute them. In this way you save time in navigating to SAPQuality Center by HP UI. If the test case execution fails, the test engineer notes down the new inputrequired. It might have happened that an existing field on the screen has become mandatory or newfield has been introduced.

3. Repair the test cases – Now the test case need to be modified to handle the input found in the step 2.Provide a suitable parameter value for the field in the identified test case. The test engineer can alsoeasily jump to the affected test cases in SAP Quality Center by HP by clicking on them in SAP TAO changeanalyzer module.

Note:

To accurately identify the screen component needed for feeding this new value, the test engineer may needto check the technical information of the screen in the transaction. In this way, he could accurately identifythe screen number. If the equivalent component for the screen number is not present in the BPT module ofSAP Quality Center by HP, it can be generated by the SAP TAO Inspection functionality.

4. Consolidate the test cases - The test cases which were modified need to be consolidated, so that all thehigher level test cases can get the fixed component. The consolidation can be triggered from the Change



of 143

Analyzer module itself by clicking on Repair Component after selecting the consolidated componentwhich is required to be updated.

5. Provide input data in the data table Excel sheet – The test engineer provides suitable data in the datatable Excel sheet for the mandatory input field.

6. Execute the repaired test case - The repaired test case is executed once to check whether the fix is doneto handle this new input. The execution can be done by adding the test case to Run List, from Change

Analyzer module.

Repairing Custom Code Changes11.3Many customers have a lot of custom objects which have a UI interface. These UI interfaces may be changed directlyby introducing new fields in the screen or by making existing fields mandatory. In this case, if new fields have beenintroduced, the screen components may need to be recreated so that they have the parameters for the new fields.

The repair of test cases could be handled in the following ways, depending on whether BPCA functionality is used ornot:

1. Repair without BPCA integrationIf you do not meet the prerequisite for using BPCA, repair the SAP TAO-based automated test case by thefollowing approach:1. Identify impacted test cases – The test case impacted due to software changes have to be manually

identified. The test engineer can seek this information from the introducer of the change.2. Execute the test cases – The test case needs to be executed once to check whether it’s really failing. If

the test case execution fails, the test engineer notes down the new input required. It might havehappened that an existing field on the screen has become mandatory or new field has been introduced.The execution of the test case can also be done from SAP TAO’s Run and Report module.

3. Repair screen components – The screen component needs to be re-inspected if new UI field has beenintroduced. In case of existing fields becoming mandatory, re-inspection is not required.

4. Repair the test cases – Now the test case need to be modified to handle the input found in the step 2.You provide a suitable parameter value for the field in the identified test case.

Note:

To accurately identify the screen component needed for feeding this new value, the test engineer may needto check the technical information of the screen in the transaction. In this way, he could accurately identify

the screen number. If the equivalent component for the screen number is not present in the BPT module ofSAP Quality Center by HP, it can be generated by the SAP TAO Inspection functionality.

5. Consolidate the test cases - The test cases which were modified need to be re-consolidated so that allthe higher level test cases can get the fixed component. The consolidation will automatically add oneextra column in data table Excel sheet for the new parameter value, e.g. DT_XXXX_XXXX.

6. Provide input the data table Excel sheet – The test engineer now needs to provide suitable data in thedata table Excel sheet for the mandatory input field.

7. Execute the repaired test case – The repaired test case needs to be executed once to check whether the

fix done to handle this new input. The execution of the test case can also be done from SAP TAO’s Runand Report module.

2. Repair using BPCA Integration



of 143

1. Identify impacted test cases – The impacted test cases can be easily identified in SAP TAO using itsChange Analyzer module. In this module, you enter the BPCA ID, which is generated in SAP SolutionManager. The ID could also be easily searched by providing suitable SAP Solution Manager Projects orSolutions.

2. Execute the test cases – You can run the impacted test cases from SAP TAO, and you do not need tonavigate to SAP Quality Center by HP to execute them. In this way you save time in navigating to SAP

Quality Center by HP UI. You can add impacted test cases to the “Run List” in SAP TAO . If a test caseexecution fails, the test engineer notes down the new input required. It might have happened that anexisting field on the screen has become mandatory or new field has been introduced.

3. Repair screen components – The screen component needs to be repaired (re-inspected) from theChange Analyzer module of SAP TAO

4. Repair the test cases – The test case needs to be modified to handle the input found in the step 2. Youprovide a suitable parameter values for the field in the identified test case. The test engineer can alsoeasily jump to the affected test cases in SAP Quality Center by HP by clicking on them in the SAP TAOChange Analyzer module.

Note:

To accurately identify the screen component needed for feeding this new value, the test engineer checks thetechnical information of the screen in the transaction. In this way, he can accurately identify the screennumber. If the equivalent component for the screen number is not present in the BPT module of SAP QualityCenter by HP, it can be generated by the SAP TAO Inspection functionality.

5. Consolidate the test cases – The test cases which were modified need to be consolidated so that all thehigher level test cases can get the fixed component. The consolidation can be triggered from ChangeAnalyzer module by clicking on Repair Component after selecting the consolidated component which isrequired to be updated.

6. Execute the repaired test case – The repaired test case needs to be executed once to check the fix doneto handle this new input. The execution can be done by adding the test case to Run List from ChangeAnalyzer module.

12 Example for Test Case RepairRepair Using BPCA Integration12.1

12.1.1 Customizing Change - PO Number has become mandatory in VA01transaction

The standard VA01 transaction is modified via IMG configuration to make PO number a mandatory field.

1. Identify impacted test cases – The impacted test cases are identified by feeding in BPCA result ID in theChange Analyzer module of SAP TAO. The suitable BPCA result ID is searched by giving a suitable projectname.



of 143

2. Execute the test cases – The test case is executed from SAP TAO’s Run and Report module. The test casecan be easily added to “Run List” by selecting it and clicking on “Add to Run List” button.



of 143

The test execution fails to point that the PO number is a mandatory input.

3. Repair the test cases – To accurately identify the screen component needed for feeding this new value,the test engineer checks the technical information of the PO number of the VA01 transaction. Thescreen component is already present in BPT module of SAP Quality Center by HP.He drags and drops the component at a suitable location and provides the required parameter value.



of 143

He also provides the suitable parameter value.

4. Consolidate the test cases – The Create Sales Order consolidated component is repaired from theChange Analyzer module.



of 143

The repair of the consolidated component also provides suitable name for the new column in the datatable Excel sheet.

5. Provide input data in data table Excel sheet – The test engineer provides the suitable data in the datatable Excel sheet of the Create Sales Order test case.



of 143

6. Execute the repaired test case – The test case is executed again from SAP TAO, and this time the testcase passes.

12.1.2 Custom code change – New input field is introduced in Custom VA01transaction

A custom VA01 transaction is created for the purpose of showing the repair using SAP TAO Change Analyzer module.This new sales order creation transaction is a one step process; it creates an order just by entering few mandatoryfields.

Now, a transport has been done, and we use BPCA and SAP TAO to identify the impacted test cases andsubsequently repair them.

1. Identify impacted test cases – The impacted test cases can be easily identified by feeding in the BPCA

result ID. The result ID can is searched on the basis of a SAP Solution Manager project.



of 143

2. Execute the test cases – Cust_Create Sales Order test case is shown as an impacted test case in theChange Analyzer module. The test case is added to Run List for execution.

3. Repair screen components – The screen component is repaired (re-inspected) from SAP TAO.



of 143

5. Repair the test cases – The test case is repaired by just providing parameter value for this new field.

6. Consolidate the test cases – The consolidated component is repaired from the Change Analyzer moduleof SAP TAO.

7. Provide test data in the data table Excel sheet file.8. Execute the repaired test case – The test case is executed again from SAP TAO’s Run and Report module,

and this time it passes.

Repair without BPCA Integration12.2

12.2.1 Customizing Change - PO Number has become mandatory in VA01transaction

The following steps explain the repair process:

1. Identify impacted test cases – The impacted test cases can be identified in the following ways:a. Discussing the impact with introducer of the changeb. Going through the transport



of 143

c. Executing the relevant automated test cases2. Execute impacted test cases to know if it fails and where

a. Execution can be done from SAP TAO Run and Report module.

b. The SAP TAO report can point the error and screenshot captured by SAP TAO log can show moredetails.



of 143

4. Repair the test cases – To accurately identify the screen component needed for feeding this new value,the test engineer checks the technical information of the PO number of the VA01 transaction. Thescreen component is already present in BPT module of SAP Quality Center by HP.

He drags and drops the component at suitable location and provides the required parameter value.

He also provides the suitable parameter value.



of 143

7. Consolidate the test cases – Consolidation is done to incorporate the changes done to the test case sothat all the higher level test case benefit out of the change. All the higher level test cases areautomatically added to the consolidation.



of 143

The repair of the consolidated component also provides a suitable name for the new column in the datatable Excel sheet.

8. Provide input data in the data table Excel sheet – The test engineer provides the suitable data in the datatable Excel sheet of the Create Sales Order test case.



of 143

9. Execute the repaired test case – The test case is executed again from SAP TAO, and this time the testcase passes.

12.2.2 Custom code change – New input field is introduced in Custom VA01transaction

The following section explains how to repair a change introduced in a custom sales order creation transaction. Thedetails regarding transaction are provided in the section “Repairing with BPCA Integration”.

1. Identify impacted test cases – The impacted test cases can be identified in the following ways:a. Discussing the impact with introducer of the changeb. Going through the transportc. Executing the relevant automated test cases

2. Execute impacted test cases to know if it fails and where – The affected test case can be executed fromSAP TAO itself. Execution can happen from Run and Report module.

The SAP TAO logs can provide details about reason of failure, which is new mandatory field in the screen.



of 143

3. Repair screen components - The screen component is repaired (re-inspected) from SAP TAO.



of 143

4. Repair the test cases – The test case is repaired by just providing parameter value for this new field.

5. Consolidate the test cases – The consolidated component should be re-generated from SAP TAOconsolidation module. All the higher level test cases are automatically added to consolidation list.Consolidation also adds extra column to the data table Excel sheet.



of 143

9. Provide test data in the data table Excel sheet file



of 143

10. Execute the repaired test case – The test case is executed again from SAP TAO’s Run and Report module,and this time it passes.

13 Known LimitationsIn this section, we describe the know limitations for important UI technologies:

Description SAP Note

CRM 1762870



of 143

14 Advanced

Login Schema14.1

To be able to automate web scenarios, the recorder and the execution engine must be able to log automatically into

the System under Test, using its login page. Since a login page can be different on each tested system, the user needsto define a login schema to describe how the login page is, by specifying Uniform Resource Identifiers of the UIelements.

A login schema can define Uniform Resource Identifiers (URI) of input fields, buttons, checkboxes, links, etc.

To ease the definition of login schemas, a user can use an assistant which will help him/her to define the UniformResource Identifier (URI) of the login page elements.

With SAP TAO comes a login schema called “NW_STANDARD_LOGON” which can be used to record and to executetestscripts on SAP NetWeaver Java systems with at least version 7.01.

All login schemas are stored on the file system, under the CBASE directory.

14.1.1 Login Schema Structure

A login schema contains three different parts: pre-login steps, login steps and post-login steps. Each part containssome actions. An action is defined by an URI and an optional value. This value is used when the action needs aparameter, for example to set a value in an input field or to select a checkbox (in that case, the value would be“checked”). Of course, it is not possible to define a value for the user field, the password field and the login buttonsince this makes no sense.

14.1.1.1 Pre-login Steps

This part can be used to perform mandatory actions before entering the username and the password. The user can

define as many actions as he wants.



of 143

14.1.1.2 Login Steps

This is the main part of a login schema. This is where the user will define the URI of the username field, the URI ofthe password field and the URI of the login button.

Additional URI can also be defined if the login screen contains some other fields, for example to specify thelanguage. Such actions will be performed before pressing the login button.

14.1.2 Post-login Steps

If some steps are mandatory once the login button has been pressed, some post-login actions have to be defined. Asfor pre-login steps, the user can define as many actions as he wants.

14.1.3 Login Schema Definition

To create a new login schema, from the Web Application executable object window, press the login schemabutton.

The list of existing login schema found on the file system (in the folder“%FF_ROOT_PATH%CBASE\ Login_Schema”) will be displayed, press the “New” button to display the loginschema creation assistant.

The same mechanism as th e “Object Spy” and the “Add Checkpoint” exists here, by specifying the Internet Explorersession it is possible to automatically retrieve the URI of a login screen UI element.

To do so, using Internet Explorer, first navigate to the login page of the System under Test.



of 143

Back to the login schema definition assistant, press the “Refresh” button and select the session whichcorresponds to the login page.

Press the “Spy” button of the “User Field URI”. In the login page in Internet Explorer, UI elements under themouse should be highlighted. Sel ect the “User” field .



of 143

Repeat this operation to get the URI of the password field and the URI of the login button.

Now the main part of the login schema has been defined. If some actions have to be performed beforepressing the login button, use the additional login steps.

If some actions have to be performed before setting the username, repeat this operation using the pre-loginsteps part.



of 143

If some additional actions have to be performed after pressing the login button, repeat the operation usingthe post-login steps part.

Once all needed steps are filled, give a name to this new login schema, an optional description and press the“Ok” button. Please note that there is an option to overwrite any existing login schema with the same name.

If this option is not selected, a counter suffix will be appended to this new login schema name. Then, this new login schema can be selected from the list.



of 143



of 143

15 FAQ

TBOM Creation15.11. Why can’t I establish an association when the system entry in the SAP Logon only contains the IP address

of the host?

SAP TAO uses the configured entry for the system under test in SAP Logon to enable SAP Solution Managerto start/stop/evaluate traces on the system under test. As the 3 character SID given in the SAP Logon doesnot allow to determine system under test, additionally the message server host must be given. Resolving themessage server host from the IP address is not possible; therefore you need to provide the message serverhostname.

2. Although I successfully established an association, the execution of the test for TBOM creation does notwork. Why?

There are several possible reasons, in general establishing an association has fewer restrictions than test

execution for TBOM creation:a. SAP TAO allows you, for example, to establish an association although you are not connected to anysystem under test. But, for executing the test you need to be connected to the system under test.

b. SAP TAO verifies at association point in time that the managed target system of a test is part of thelogical component in the blueprint executable, but it needs not to be the chosen one. At executiontime you need to have chosen the valid product system of the logical component, therefore it mightbe necessary to modify the system role to point to the appropriate product system. Note that thesystem role is user-specific, therefore you need to logon with the same user ID to your SAP SolutionManager as used in SAP TAO to adjust the system role.

c. The user IDs used in SAP TAO for both the SAP Solution Manager system connection and the systemunder test connection must be identical, due to usage of trusted RFC connections

d. The user IDs registered in the “LaunchAndLogin” component of the SAP Quality Center by HP testmust match the user IDs SAP TAO used on the system under test to record and evaluate traces.

3. Although the execution for TBOM creation went well, no TBOM was created in the executable item of theproject. Why?

a. For evaluation of the recorded traces on the system under test, trusted RFC connections must havebeen configured: A connection from your SAP Solution Manager System to the system under test,and also a back connection from the system under test to Solution Manager.

b. If a TBOM already existed for the executable item when you started TBOM creation within SAP TAO,it might be that a subordinate TBOM was created but you don’t see it. Those subordinate TBOMs areonly visible when you have set a user parameter on your Solution Manager System(AGS_BPCA_TBOM_CHILDS X,http://help.sap.com/saphelp_em70/helpdata/en/6a/334954d76e498da73d44a7951372fc/frameset.htm )

4. Do I need to have the same user for TBOM creation in SAP Solution Manager and the system under test ifthere is trusted connection between them?

Yes, the user which is used to connect to SAP Solution Manager from SAP TAO must also be present in thesystem under test.

Miscellaneous15.2

1. Why are some SAP GUI sessions closed when I execute SAP TAO-based test cases?

http://help.sap.com/saphelp_em70/helpdata/en/6a/334954d76e498da73d44a7951372fc/frameset.htm







of 143

SAP TAO closes all SAP GUI sessions before executing a test case. Only those sessions are closed, where scripting isenabled on the server.

16 Appendix

Citrix and SAP TAO16.1You may have a Citrix-based server landscape for testing purposes. The Citrix software installation on a serverenables it to be accessible over the web. Multiple users can access the server via a web URL.

The benefits for having a Citrix-supported system landscape are the following:

You can have a central Citrix server with all the software installed on it e.g. SAP TAO, SAP Quality Center byHP Client, HP QTP, etc.

The central Citrix server may also provide testing efficiency, if it’s located near to the test systems.

A Citrix-supported system landscape supports geographically distributed test teams.

SAP TAO was tested on the following Citrix severs:



of 143

Operating System Citrix Version Architecture

Windows Server 2008 Citrix 5.0 64

Windows Server 2003Enterprise Edition

Citrix 4.5 32

Component for Support Messages16.2For issues faced in SAP TAO, open support message for the component SV-SMG-TAO .

See Also16.3

For more information, see the following resources on the SAP Service Marketplace:

User guide available at http://service.sap.com/instguides SAP Components SAP Test Acceleration andOptimization

Application Help available at http://help.sap.com Application Lifecycle Management SAP Test Acceleration and Optimization <Current Release>.

SAP TAO webpage at http://service.sap.com/saptao .

http://service.sap.com/instguides



http://help.sap.com/










www.sap.com/contactsap

© 2013 SAP AG or an SAP affiliate company. 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. Nationalproduct specifications may vary.

These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational pu rposes only, without representation or warranty of any kind, and SAP Groupshall 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 warrantystatements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP 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 other countries.

Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

SAP TAO Guide.pdf

Documents

Transcript of SAP TAO Guide.pdf