Viewing test logs

To see a record of all the events that occurred during a test run or a schedule run, as well as the status of each verification point, open the test log for that run. You can also compare an event from the test log with the request or response in the test to view the differences between the recording and the playback of the test.

About this task

The test log file is stored in binary format with a .executiondlr file name extension in the project directory of your workspace. You can also view the test log in the user interface.

Procedure

  1. In the Test Navigator view, right-click the executed test; then click Display Test Log.
  2. On the Overview tab, view the verdict summary for the executed test. To see the potential data correlation errors in a separate view, click Display Potential Data Correlation Errors.
  3. On the Events tab, view the errors, failures, and passes for each event in the test.
    • To navigate to the verdict type, click the Select the verdict type Select the verdict type icon.
    • To compare an event or request in the test log with the response or request of the test, right-click an event and click Compare With Test > Request, Compare With Test > Response Data, or Compare With Test > Response Headers. The compare editor highlights the differences.
  4. On the Data Correlation tab, see all the references and substitutions that occurred during a test execution, as well as the data correlation errors. By default, you view both references and substituters. To view only substituters, click the Show References Show References icon. To view the correlation data for each virtual user that was executed, click the Merge Users Merge users icon. This icon is enabled only for a schedule. In the Data Correlation section, when you click an event, you can see the correlation data in either the Content View or the Table View.

What to do next

From the test log, you can submit, search, and open defects in a defect tracking system. For details on configuring the test log preferences and working with defects, see Associating defects with a test log.