Create new and better report on TestStand

[Tomerfl]

Hi,

TestStand has some types of reports. 

Today we are using the ATML 5, the default template. But unfortunately we found it not comfortable to read and to work with.

I want to create a new report that looks more modern and present the data more organized and easier to read and navigating.

I tired to do that with all of the customizations options, but i found all of them not so friendly and didn't succeed to improve the existing reports.

Do you work with the default and the existing reports? What did you do to improve the reports? did you create a new one? Are you using third party tools to create better report at the end of the the running tests?

[santo_13]

A fancy report customization is possible but may not be for a beginner.

In short, Report Plugins get the result from the step as an object, the logic implemented in the report plugin understands the result object and formats it into the report. 

ATML5 report plugin was built by NI with some flexibility to enable users to customize the report without any coding.

TestStand Report Generation and Customization - NI

Another option is the offline report processing utility - Product Documentation - NI

[python007]

Hi to all

We use the ATML 6.01 default template and I agree it is realy not comfortable to read and to work with and NI should improve it.

I already had some questions to NI about modifing the existing Stylesheets with this answer:

So I tried it with the help of ChatGPT and i could modify it that the Step Names are in bold:

With the Step Name in bold and a Step numbering I think it is a littel bit more readable.

What are the others users recommendations for better readability?

[Laurent_B]

Hello,

Indeed, I find the report custommization with a stylesheet too complicated.

I work with 2 reports, one is the default report with ATML format and the tr5_horizontal.xsl stylesheet. The second one is a custom report, today with a database, but it can also be with Excel, Word ...

The idea is that the default report is like a log. I have all the information about the execution of the test of a UUT, with all the step results and extra information recorded by the ReportText property and the additional results step or property.

The second report contains only results required by the test specification. I use custom step types based on the standard test step types. For example, the NumericLimitTest step type => a CustomNumericLimitTest step type with extra properties and a pre-step to record the result.

So to summarize, one default report as a log, one custom report with only the results needed by the test specification.

Laurent