How to Debug Tests and Flows Containing Automated Components

This task describes how to debug tests and flows to make sure that they run properly.

This task is part of a higher-level task. For details, see Plan business process tests and flows.

1. Prerequisites

   • Make sure that the flow or business process test that you intend to debug contains only automated components.

   • Ensure that the components you intend to debug have either scripted GUI or keyword GUI automation.

   • Ensure that default values are set for all parameters. For task details on setting values, see How to Set Parameter Values.

   • UFT One: To be able to debug or run flows and business process tests that contain automated keyword GUI business components, or view test results, make sure that one of the following is installed: 

     • QuickTest Professional version 10.00 or 11.00

     • UFT One version 11.50 or later

   • UFT One: Close all browsers before running a test on a Web browser. UFT One must load the Web Add-in (as defined in the application area in UFT One) before a step in the test opens the browser.

   • UFT One: If the test contains UFT One components, the test should include a UFT One component at the beginning of the test before the browser opens.

2. Debug automated tests and flows

   In the Test Plan module, select the relevant test or flow in the Test Plan tree. Start debugging by clicking in the Test Script tab. For user interface details on the Run or Debug test dialog box, see Run or Debug Test Dialog Box.

3. Monitor the debug run

   While running a test or flow in debug mode, you can monitor the debug run.

   • From your task bar, you can toggle between the Test Plan module, the testing tool (such as UFT One), and the application you are testing.
   • In the Test Plan module, the status of the test and the name of the component currently being run are shown below the toolbar in the Test Script tab, for example, Running(OrderStart). You can click the Stop Run button to stop the run at any time.
   • In the relevant testing tool, the status of the test being run, for example Running, or Ready, is shown in the status bar at the bottom of the window.
   • UFT One Keyword GUI or GUI Scripted: All the debugging functions from the Debug menu, for example, Step Over or Step Into, are enabled for use. For details on applicable debug options, see the Micro Focus Unified Functional Testing User Guide.
   • UFT One Keyword GUI or GUI Scripted: If you selected a business component to run in Debug mode, the test pauses after opening the component in UFT One. Use the UFT One debug options to control the continuation of the run through the displayed component. When you are ready to proceed with the run, continue the run in UFT One.
   • When one component finishes running, it closes and the next component in the test opens in the testing tool.

4. Results

   When the debug run is complete, ALM imports the results from the testing tool and displays summary information in the Debug Run Information dialog box.

   For user interface details, see Debug Run Information Dialog Box.