DevOps Automation

Earlier to this article, Chris Haggan and Shivi Sivasubramanian created a blog posting of the new 9.1.1 Reporting Dashboard, also known as Unified Reporting (Reporting and viewing test outcomes made simpler than ever).

​This article goes one step further and shows you how to configure Performance Tester to use the dashboard and publish a report.

It is assumed the Reporting Dashboard is installed and up and running.

​Prerequisites

​The URL of the Reporting Dashboard must be located.  For instance, when Rational Test Control Panel and Performance Tester are on the same machine, we can use https://localhost:5443.

How to configure Performance Tester

4 . If the connection works, then click Apply or OK.
​5. Choose the appropriate value from the drop-down list.
The following values determine when to publish a report and when a test or schedule completes the execution:

• Never
• Prompt
• Always

Never: Performance Tester neither automatically publishes nor prompts to publish a report after a schedule or test execution.  

Prompt: At the end of a run, Performance Tester prompts whether the report should be published.  If the execution fails and we don't want to share the results, then answering “no” to the prompt prevents the report from being published.

Always: The report will be published regardless. 

How to publish a report with Publish result after execution set to “Never”

Right-click the result you want publish and choose Publish...
A dialog box is displayed.  If no project was created, you can still create or choose an existing project.  If you don’t have existing projects, you can create one and say, BlogProject.

​Click Finish to publish the report.

How to publish a report with Publish result after execution set to “Prompt”

​After the execution is complete, a Result Publication dialog box is displayed.  Click Yes to publish the report.

How to publish a report with Publish result after execution set to “Always”
Here, the report is published automatically and no extra effort is required.  You should use this option only when needed because you might forget that it was selected and it might create many unwanted reports on the Reporting Dashboard, which you have to delete manually.
This option is useful if you are running a schedule or test from the command line and you want the results to be published.  However, the Prompt setting also results in the report being published.

You must run the following command to run the schedule "cmdline_10VURTCP":
​
cmdline-eclipsehome "C:\Program Files\IBM\SDP" -plugins "C:\Program
Files\IBM\IBMIMShared\plugins" -workspace "C:\IBM\00000-000-000-Blog" -project
​"UnifiedReporting" -schedule "Schedules\cmdline_10VURTCP" -exportstatshtml c:\temp

​As expected, the result is published to the Reporting Dashboard.

Conclusion
Publishing reports from Performance Tester to Reporting Dashboard is easy and straightforward. It works when running a schedule or test from the GUI and from the command line.

Paul Liskay
​Support Engineer

Paul Liskay joined the Rational team in 2009.  Currently, he is a Level 2 Support Engineer for the Rational Testing Tools for the US geography, focusing on Rational Performance Tester, Rational Integration Tester, and Rational Test Workbench Web UI.   Before joining the support team, he has led the teams for the Rational Integration Tester 8.0 release and for Rational Performance Tester for the 8.0 through 8.2 releases.  He was also with the system test team for Rational Team Concert for the 4.0 release.