Viewing stub logs

IBM® DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) enables IBM DevOps Test Virtualization (Test Virtualization) users to view the console output of stubs that ran in the selected domain and environment.

You can see the results only if logging to a project results database is enabled when the stub is deployed. To verify that the stub was configured to log, check the Environments Dashboard for Test Virtualization Control Panel (or in IBM DevOps Test Integrations and APIs (Test Integrations and APIs)). If a domain-level project results database override was set up for the selected domain, only the results database specified in the override is used for displaying the console output of stubs in that domain.

If no overrides exist, the results databases for all projects published to the currently selected environment that contain the selected stub are used to display the console output of that stub.

When stub logs are viewed, the connection to the specified project results database is made from the system running Test Virtualization Control Panel. When a stub writes its logs, the connection is made from the system running the agent upon which the stub is running. (This may not be the system running Test Virtualization Control Panel.)
Note:
When you set the logging level to Normal, log messages are written to the project results database. When you set it to Debug, more messages (in addition to those found in the project results database, if any) are written to the IBM DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent) log file. The following procedure applies to viewing the logs that are only stored in the project results database.
  1. On Test Virtualization Control Panel Results page, specify the results database and the stub for which, you want to view the log details.
  2. Enter a date range if applicable, and click Search.
  3. Select the stub from the results to display the activities performed.
    Note:
    If the log panel is not displayed or if an empty log panel is displayed, refer to Troubleshooting stubs.