January 13, 2009

Report Publishing

Helix ALM

Works with TestTrack 2009, 2010.0.1 and later

Will not work with TestTrack 2010.0, upgrade to maintenance release

Will not work with TestTrack 2008 and earlier

The new SOAP reporting calls in TestTrack 2009 enable some pretty exciting automation possibilities with TestTrack reporting. You'll find a collection of samples on this page, all aimed at improving your access to TestTrack reporting.

Online Dashboard

This sample provides a web interface to all of your TestTrack reports by project, without requiring users to login through the TestTrack web client. Instead, authentication is hard-coded through the SOAP API, allowing seamless use of the product. Download the Web "Dashboard" zip file.
  • Seapine Reports Dashboard.php - Folder containing sample written in PHP 5.
    • Near the top of index.php, set the correct SOAP server address along with username/password for your TestTrack installation.
  • Seapine Reports Dashboard.js - Folder containing sample written in JavaScript/AJAX, with a little PHP for server-side file caching.
    • Near the top of index.php, set the correct SOAP server address along with username/password for your TestTrack installation.
    • Near the top of index.php, set strProxy to either proxy.php or proxy.aspx, depending on which web server you're running on.
  • Seapine Reports Dashboard.Net - Folder containing sample written in ASP.Net.
    • Near the top of index.aspx.cs, set the correct SOAP server address along with username/password for your TestTrack installation.
To use this effectively, you need to create a dedicated TestTrack user account. Then, either create private reports for that user, or add the user to a dedicated security group and share reports with that group. This allows you to control what reports are available from the interface.

Report Publishing

This sample consists of a C#.Net application with both a GUI and CLI front-end. The GUI isn't very different from the web "dashboard" available on this page. It is a locally-run application and require users to login with their own TestTrack account, which is important in some environments. The more interesting piece is the CLI, allowing you to execute a TestTrack report and save it to disk. The use-case here would be to schedule it to run at a defined interval, dumping report results into a web server that people can visit at their leisure. Additionally, you could add functionality to send email and have the CLI fire off the report every Sunday morning to emails addresses of your choosing. Download the report publishing application zip file.
  • SRP Installer.msi - Installer for the application, includes executable files and source code.
  • srp.py - Python implementation of the publishing app (CLI only).
Note: Seapine does not provide support for sample scripts. Note: If "Array cannot be null" error is returned using the .NET version of this application, try using Apache as the web server. Seems to be an issue with IIS saving the temp files that the reports generate. These temp files are required to display the report. Note from an end-user on 4/05/2010: On IIS 7, the local user account IUSR (which will not appear in the list of users) must be granted file/folder permissions to the C:%windir%temp folder. It is not enough to grant the local group IIS_IUSRS permissions to this folder. Not sure the minimum permissions needed, but granting Full Permissions to IUSR (the IIS anonymous/guest user account) should solve reports coming up in an empty window (though this may be a security issue for some sites). For IIS 6, you may need to do the same thing for the IUSR_MachineName local user account. ENHANCEMENT REQUEST TO SEAPINE: please change ttsoapcgi.exe to let you specify the temp folder it will use.