Publishing test results to the server

The test results indicate the quality of the application under test. Different stakeholders might want to check the quality of the application but do not have the desktop client installed. As a desktop client user, you can publish test results to IBM® DevOps Test Hub (Test Hub) so that others can view them from the web browser.

You must have completed the following tasks:

  • Accessed Test Hub.

  • Created an offline user token to connect to Test Hub from Test Performance. For more information, refer to Managing access to the server.

  • Created or joined a project in Test Hub.

  • Upgraded legacy reports to the Web Analytics report format.
    Note: You can right-click the report and select Upgrade to upgrade the legacy report to the Web Analytics report.

  • Configured the firewall so that Test Hub enables connection on port number 443.

You can publish both performance and functional reports. You can set the publish parameters 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 parameters, the test result is published to Test Hub after the test run is complete.

If you select Prompt from the drop-down list for the Publish result after execution option, after each test run, the Publish Result dialog is displayed to publish test results to Test Hub. You can modify the following options before publishing the results:

  • If you want to publish reports to other than the default server added in the Preferences window, you can change the URL of Test Hub.
    Note: If you change the server URL, you must enter an offline token to enable the publishing of test results.

  • The default value for the Result Name field is the test result that you selected. You can provide a different name that you want to use.

  • To identify specific test results, you can enter a name in the Labels field to associate it with the test result.

    Note: The Results page of Test Hub displays the labels that you added in the Labels field.
  • You can change the project name if you want to publish reports to a different project.
    Note: The Project Name drop-down list displays all the projects on Test Hub. The name of the team space for the project is displayed within parenthesis. You can select the appropriate project when there are identical project names in different team spaces.

    If there are no projects or if you are not a member of any project or team space, then you must create a project or become a member of a project or team space on the server.

You can publish large test results from Test Performance to Test Hub. When you publish large test results then the report publishes to Test Hub in chunks of predefined size.

  1. Click Window > Preferences > Test > DevOps Test Hub.
  2. Specify the URL of the server and click Test Connection.
    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. Enter the offline user token that you generated on the server and click OK.
  4. Optional: Click Manage Offline Tokens to view and remove the tokens that are associated with the desktop client, and click Apply and Close.

    For example, if there is one instance of the desktop client for multiple testers to publish reports, each tester must remove the token created by other testers and add a new token.

  5. Click the Results page from the navigation to apply settings for publishing reports.
  6. Clear the DevOps Test Hub Use default URL checkbox if the URL of the server is different than that is specified at Window > Preferences > Test > DevOps Test Hub.
    The format of the URL is https://fully-qualified-domain-name:443.
  7. In Publish result after execution field, select when to publish test result.
    In the initial stage when you are debugging a test, you might not want to publish the test result. Select one of the following options based on the requirement:
    • Select Never to never publish the test results to the server.
    • Select Prompt to prompt you to publish the test results after every test run.
      Notes:
      • A command-line interface always publishes test results to the server even if the product preference is set to Prompt.
      • After each test run, the Publish Result dialog is displayed to publish reports to Test Hub.
    • Select Always to publish test results after every test execution.
  8. In Publish to project field, select a project that you are a member of on the server.

    The Publish to project drop-down list displays all the projects on Test Hub. The name of the team space for the project is displayed within parenthesis. You can select the appropriate project when there are identical project names in different team spaces.

    You cannot create a project from the desktop client. If there are no projects or if you are not a member of any project or team space, then you must create a project or become a member of a project or team space on the server.

  9. In Reports, select the reports that you want to publish to the server.
  10. Click Apply and Close.
Test results are published to the Test Hub, depending on the parameters that you have set.

You can log in to Test Hub and analyze the test results. For more information refer to Test results and reports overview.