Test Script Debugger CBTA 3.0 SP11 Document History

Home , Test automation

Test Automation - User Guide PUBLIC SAP Solution Manager 7.2 2018-12-03

CBTA - Test Script Debugger CBTA 3.0 SP11 Document History

Version Date Change

1.6 2018-12-03 CBTA 3.0 SP11 Update

1.5 2018-05-15 CBTA 3.0 SP10 Update

1.4 2017-09-30 CBTA 3.0 SP9 Update

1.3 2017-03-01 CBTA 3.0 SP8 Update

1.2 2014-05-27 CBTA 3.0 SP2 Update

CBTA - Test Script Debugger 2 Document History Table of Contents

1 Running a CBTA Test Script in Debug Mode...... 4

2 How-to start ...... 5 2.1 Add or remove breakpoint...... 8 2.2 Step Over...... 9 2.3 Run...... 9 2.4 Stop Debugger...... 9 2.5 Error Behavior ...... 10 2.6 Dynamic Report...... 11 2.7 Launch Object Spy...... 12

3 How to Connect an External Debugger to CBTA debugger...... 13 3.1 Preparation...... 13 3.2 Starting the external debugger ...... 15

If a CBTA test script does not work, you can execute the components (test steps) one by one. Component-Based Test Automation offers a graphical overview of the test steps and displays the corresponding UI component attributes. The CBTA debugger allows you to debug a test while remaining at the component level, without seeing the Visual Basic Scripting (VBS) code lines. Therefore, you see the actual state of the tested application UI, as well as input and output parameter values.

To examine the VBS code, you can use the Microsoft Visual Studio debugger. See Section 3 - How to Connect an External Debugger to CBTA debugger

In Solution Manager 7.2, use transaction SM_WORKCENTER to start the Solution Manager Fiori LaunchPad. 1. Select Test Suite group. 2. Open Test Repository (test configuration or test scripts)

You go to the Start Options screen.

5. Choose Execute.

The CBTA debugger is started. A graphical overview of the test steps is displayed.

CBTA - Test Script Debugger PUBLIC How-to start © Copyright 2018 SAP SE. All rights reserved. 7 The point hit of test script step is highlight the component box in yellow and blue arrow marker is add on component box.

2.1 Add or remove breakpoint

Two possibilities to add ore remove a test step breakpoint: - Select one component and choose the Toggle Breakpoint button - Double click on one component

When a breakpoint is configured a red circle marker is add into component box selected.

· To change parameter values dynamically, double-click them in the table, edit the new value and press enter. · To examine the code, choose the Start External Debugger pushbutton. See chapter Error! Reference source not found.

Shortcut key: F4

In case you would move to the next component in your script, click on toolbar button Step Over. CBTA debugger will execute the current action of default component before to stop test execution on next component. Shortcut key: F6 ,F10

2.3 Run

In case you would move to the next breakpoint active in your script, click on toolbar button Run. CBTA debugger will execute the all components until to stop test execution on next component. Has breakpoint marker. Shortcut key: F5 , F8

2.4 Stop Debugger

If you would stop the debugging session, click on toolbar button Stop. The test execution is stopped and the test report will be displayed. Into test report a message is available the test script has been stopped by debugger.

In case of error during execution, the error message is displayed in the status message at the bottom of the CBTA debugger window.

More information can be seen by using the tooltip onto this status bar message (just leave your mouse some seconds without moving onto the error message to get the tooltip displayed).

Once an error happens, you need to press the Run button to end the execution and go back to the SAP GUI session (with the Start Options screen) to display the execution report.

The report tab dynamically shows the HTML type report being constructed after each component execution.

To analyze some control display into the application in real time, you can launch the Object Spy application in clicking on toolbar button Object Spy.

The spied session is not opened by the Object Spy. You need to select into Object Spy session selector.

This chapter describes a step-by-step procedure to initialize and use Visual Studio as external debugger for CBTA test script. Visual Studio 2010 is the only supported external debugger.

3.1 Preparation

In Visual Studio, open the Tools/Attach to process menu.

Press Select, check the Script entry, then Ok on the little popup window, and finally press Cancel on the larger window. This setting remains set even if you close Visual Studio.

In the CBTA debugger window, choose the External Debugger button.

Visual Studio opens and shows a default Solution:

CBTA - Test Script Debugger PUBLIC How to Connect an External Debugger to CBTA debugger © Copyright 2018 SAP SE. All rights reserved. 15 It is important to understand that there are now two debuggers on the same VBS code:

- First one is the CBTA debugger that is a COM object called by the VBS script. So it is not a real debugger but rather a dot net UI showing the current state of execution and also allowing communication with the program to get and set parameter and execution context values. - The second one is the Visual Studio debugger (called external debugger). It is also attached to the same VBS script.

Press the pause button in Visual Studio to stop on the next VBS instruction.

The “eval” code in the Solution contains the CBTA CBASE function (library of functions, subs and variables). The other file with the vbs extension holds the test script code. We can see the VBS interpreter program is wscript.exe.

Choose Run or Step Over button in the CBTA debugger to give back execution to the VBS script. It is recommended to choose Run.

Visual Studio pauses the execution to the next VBS instruction. This is located in the function used to communicate with the CBTA debugger.

It is now possible to use all the Visual Studio functions like Step Into, Step Over, Step Out, variable edition, call stack etc.

CBTA - Test Script Debugger PUBLIC How to Connect an External Debugger to CBTA debugger © Copyright 2018 SAP SE. All rights reserved. 16 Please note that before each component execution, the CBTA debugger will be called again by the VBS script. If you have pressed the Step Over button or defined a breakpoint in the CBTA debugger, then it will block execution. If you chose Run, then it will not stop the execution.

The Visual Studio commands act as a lower level (VBS instruction) than the CBTA debugger (component level). Visual Studio leads the VBS script execution.

The CBTA debugger is called by the VBS script during execution.

© Copyright 2018 SAP SE. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System ads, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.