NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Update ATML Report Header with Data gathered during test execution?

Solved!
Go to solution

I need to add data obtained during test execution to the (ATML TR5/6_Horizontal.xsl) report header. I have tried to implement any/all of the update features I have seen here to no avail. I can get things added if I do it during PreUUT but I don't have this data yet. Trying the same commands (using the Parameters.UUT.AdditionalData container) isn't working. I haven't been able to get the ModifyReportHeader callback to do this either. The help and other support examples I have seen seem to be about half of what I need to implement this. Any help is appreciated.

-Randy

0 Kudos
Message 1 of 5
(3,585 Views)
Solution
Accepted by topic author RGTer

Hi,

 

ModifyReportHeader would be this first thing I would try - what kind of problems did you have when you tried this?

 

Have you read through the following KnowledgeBase?  How to Modify a TestStand XML Report Header

 

Regards,

Charlie Rodway | Principal Software Engineer | Certified TestStand Architect (CTA)

Computer Controlled Solutions Ltd | NI Silver Alliance Partner | GDevCon#1 Sponsor

0 Kudos
Message 2 of 5
(3,542 Views)

BTW, I am using TS2014, 32-bit version.

 

The properties show up in the xml file but are not displayed as part of the header using the ModifyReportHeader callback (modified). Since ModifyReportHeader is called multiple times during the test sequence execution, is it not overwriting the value when the value becomes known? That is, is only the first write happening? And why doesn't it still show up in the header?

I am successful getting data into the report header via updating the Parameters.UUT.AdditionalData.Set<datatype>(...) command followed by the statement Parameters.UUT.AdditionalData.SetFalgs("",0,PropFlags_IncludeInReport) if this is called from PreUUT callback.

This doesn't work for my condition where I try to update with data collected during the test execution.

One thing I noticed in the Configure Report Options dialog is the "Select Report Generator" section is disabled and shows DLL as the selected generator. There is a note that says ModifyReportEntry callbacks are not called. Seems like they ARE but could this be a problem?

0 Kudos
Message 3 of 5
(3,518 Views)

So, I am getting closer -- the XPATH from the example (//REPORT/Prop) is NOT //REPORT -- it is a rather long string, three levels deep. Now I can see the values but they are not in the header table itself but above it. And they have the "initial" values, not the values updated from the test execution.

0 Kudos
Message 4 of 5
(3,515 Views)

Okie Dokie! I have the data printing into the header (as part of the table). Now just refining to see if the correct data can get reported. I put a pre-condition on the execution of the statement that writes the XML so that it only executes when I "tell" it to. This seems a tad obnoxious but if it works...

0 Kudos
Message 5 of 5
(3,514 Views)