Functional test logs

After playback finishes, you can view results in the log. Results include any logged events, such as verification point failures, script exceptions, object recognition warnings, and any additional playback information.

You can view Functional Tester logs in Functional Tester or in the Test Log window of TestManager, by setting the logging preferences.


Types of logs

You can use three types of Functional Tester logs that to view your playback results. These logs contain the same information in different formats:


Location of logs

When you set the Functional Tester Log Type preference to HTML or Text, Functional Tester stores these logs in a log folder in the same location as the Functional Tester project, but not in the Functional Tester project. The name of the log folder is the project name with a suffix of _logs. For example, if your Functional Tester project is CalendarApp, Functional Tester stores its HTML or text logs in the CalendarApp_logs directory. You can open these logs from Functional Tester in the Functional Tester Projects view. If you select HTML, your default browser opens the HTML log file. If you select Text, the text log file opens in the Functional Tester script window.

In the Functional Tester Projects view, the HTML and text logs are listed within each project. Each script in the project has its own node in the logs directory. You can right-click the script log node to open, rename, delete, import, export, or view any logs or verification points it includes.

When you associate a Functional Tester project with a Rational project and set the Functional Tester Log Type preference to TestManager, the log displays after you run a Functional Tester script is a TestManager log. TestManager stores the log as part of a Rational project. For information about using the Test Log window of TestManager, see the Rational TestManager Help.


Managing logs

Use the Functional Tester Projects view to manage HTML or text logs. The logs appear underneath the project directory. Each script in the project has its own node under the logs directory. You can select a log and right-click Open Log, Final Screen Snapshot, Delete, or Rename. If your script has a verification point, you can select the log and open it in the Verification Point Editor by clicking Open VP, or open it in the Verification Point Comparator by clicking Open Comparator.

You can view the results of a verification point from the HTML log. At the end of each verification point entry in the HTML log is a View Results link. Click that link to open that verification point in the Verification Point Comparator. If the verification point failed, the baseline and actual files are shown side by side so that you can compare the data. If you get an error about the Java plug-in when trying to start the Comparator, verify that your plug-in is configured properly. For instructions, see Enable the Java Plug-in of a Browser.

To manage TestManager logs, use TestManager. You can filter log data, rename or delete log files, or run a report on a log. When you run a suite, TestManager creates and names a new log each time. For information, see the Rational TestManager Help. You can set the Functional Tester Logging preference to prompt you before overwriting a log if Functional Tester is using a TestManager log.

Note About TestManager Integration: Functional Tester is integrated with Rational TestManager version 7.0.2. If you have the 7.0.2 version of TestManager, you will be able to use the integrated features of Functional Tester and TestManager.


Related concepts

Managed logs and Rational TestManager

Log Extension

Related tasks

View results in the log

Related reference

Logging page