Publishing test result to DevOps Test Hub

The test results indicate the quality of the application under test. There could be different stakeholders to the application who do not have the product installed but want to check the quality of application. You, as the user of the product, can publish the test results to HCL DevOps Test Hub (Test Hub) so that others can view it from the web browser.

Before you begin

  • You must have installed the Test Hub and started it. The server is part of the product package. For more information about Test Hub, see the Information Center.
  • You must have created an offline user token on Test Hub, see Generating an offline token.
  • If the Test Hub server is behind a firewall, you might not be able to connect to it. You must configure the firewall so that it can allow connections on ports 5443 and 7828.

About this task

You can play back UI tests from the UI Test perspective or play back functional tests from the Functional Test perspective and generate reports in Test Hub. You can publish XML, HTML, and unified reports. You can view the Verification Point comparison only in the unified report.
Note: This feature is available only with the Eclipse-based HCL DevOps Test UI (Test UI).

You can choose to set the publish parameters once in the Preference page so that you do not have to do it after every run or you can set the parameters every time for the specific result that you want to publish. Based on the publish parameters, the test result is published after the test run. For information about how to publish specific test result, see Publishing specific results to DevOps Test Hub.

Procedure

  1. Click Window > Preferences > Test > DevOps Test Hub.
  2. Type the URL of the server in DevOps Test Hub URL and click Test Connection.
    The format is https://servername:5443.
    Note: In Linux operating systems, the Password recovery setup pop-up window is displayed, but it is hidden behind the Preferences dialog and you might not be able to close it. To work around this problem, you must press ALT+TAB repeatedly until the Password recovery setup pop-up window comes to the foreground.
  3. Specify the offline user token that you created on the server.
  4. Click Results.
  5. Select when to publish test result in Publish result after execution. In the initial stage when you are debugging a test, you might not want to publish the test result. Select one of the options based on your need.
    • Select Never to never publish the test results to the server.
    • Select Prompt to ask you to publish the test results after every test run.
      Note: A command line run will always publish the test results even if the workbench is set to Prompt.
    • Select Always to publish the test results after every test execution.
  6. Select a project that you are a member of on the server in Publish to Project. The test result is published to that project. You cannot create a new project from the desktop client. If there are no projects or you are not a member of any project, create the project or become a member of a project on the server.
  7. Select the reports that you want to publish to the server in Publish reports.
  8. Click Apply and Close.

Results

Test results are automatically published to the Test Hub, depending on the parameters that you have set.

What to do next

To view the test results:
  1. Log in to the server.
  2. Click the Results page and then expand the test.
  3. Click the published report links. The report opens in a new browser.