In Functional Tester, Java Scripting, Functional Tester scripts are recorded in the Java programming language. Debugging these scripts is the same process as debugging a conventional Java application. For more information about using the Test Debug Perspective, see the IBM Java Development User Guide (Getting Started: Debugging Your Programs). Note, however, that the Functional Tester Debug Perspective makes it easier to start the debugger included with the Java Development Toolkit.
If you prefer, in Functional Test, Java Scripting, you can debug in the Functional Tester Debug Perspective rather than the Test Debug Perspective. To do this, click Window > Preferences. In the left pane, expand Functional Tester and click Workbench > Advanced. Clear the Switch to Test Debug Perspective when debugging check box.
In Functional Tester, VB.NET Scripting, Functional Tester scripts are recorded in the Visual Basic programming language. Debugging these scripts is the same process as debugging a conventional Visual Basic application. For more information about debugging in Visual Basic, see the Microsoft Developer Network (MSDN) Developing with Visual Studio.NET (Building, Debugging, and Testing). In Functional Tester, VB.NET Scripting, more views appear when a script is in debugging mode.
To debug a script:
Configure your application for testing by setting the appropriate Java environment or Web browser as the default to run the application you are testing. For information, see Before You Record.
Open the Debug Perspective in any of three ways:
In Functional Tester, Java Scripting, in the
Functional Tester Projects view, click a script and click the Debug
Functional Tester Script button in the Functional
Test toolbar. In Functional Tester, VB.NET Scripting, in the Solution
Explorer, click a script and click the Debug
Functional Test Script button
in the Functional
Tester toolbar.
In Functional Tester, Java Scripting, in the Functional Tester Projects view, right-click a script and click Debug. In Functional Tester, VB.NET Scripting, in the Solution Explorer, right-click a script and click Debug.
In Functional Tester, Java Scripting, in the Functional Tester Projects view, click a script and from the Functional Test menu, click Script > Debug. In Functional Tester, VB.NET Scripting, in the Solution Explorer, click a script and from the Functional Tester menu, click Script > Debug.
The Test Debug Perspective opens and provides information as the script plays back under the debugger.
After the script runs, a log file is displayed. If a log is not displayed, in Functional Tester, Java Scripting, check the settings in the Logging Preferences Page. In Functional Tester, VB.NET Scripting, check the settings in the Logging Options Page.
If a verification point fails, the Comparator appears so that you can analyze the results. If the Comparator does not start, in Functional Tester, Java Scripting, check the settings in the Logging Preferences Page. In Functional Tester, VB.NET Scripting, check the settings in the Logging Options Page.
Related Topics for Functional Tester, Java Scripting:
Setting Functional Tester Preferences
Running a Script from TestManager
Running Scripts from Functional Test
Related Topics for Functional Tester, VB.NET Scripting:
Setting Functional Tester Options
Running a Script from TestManager
Running Scripts from Functional Test
Terms of use | Feedback
(C) Copyright IBM Corporation 2002, 2004. All Rights Reserved.