How to Modify Html report??

[goel]

Hello

I am using TestStand 4.0 for UUT testing.
I have generated a sequence containing some labels, i need to show these labels description in my HTML report header.
Secondly, i need to have a link generated after the report header for all the steps that got "Failed" , right now their is only one link for the first "failed" step.
Could you help me out in this its a bit urgent?

Nitin

[j_dodek]

Hi Nitin,

Check out this link there is a example how to modify the header
http://forums.ni.com/ni/board/message?board.id=330&thread.id=19031

For adding more links you can use the Callback ModifyReportEntry

Greetings

Juergen

[goel]

Thanks Juergen
It i didn't expected it to be so early

i would be trying this for my first query but i also need to implement the other query that was mentioned

**Secondly, i need to have a link generated after the report header for all the steps that got "Failed" in the html report , right now their is only one link for the first "failed" step.

nitin

[j_dodek]

Ni Nitin,

I took a look into the SequentialModel  and ReportGen_Html the link is done in the Header!
First i thought this in done in the body but this was wrong ! -Sorry-

So the ModfiyHeader callback is good place to do this.
You have to place the links by parsing the headerstring and place them at right position

OR

you could use the TestReportCallback now you can do what ever you want.

To see how NI places the a link take a look at AddReportHeader in ReportGen_Html.seq file

To list all Fail-Stuff it seems you have to parse the Parameters.MainSequenceResults list

Hope this helps

juergen
  

[nickb]

Hello Nitin,

I think that we have a very nice Dev Zone article that answers your question exactly.  Have a look at this link:

Modifying the Failure Chain of the HTML Report to Include All Failed Steps

Let us know if you have any questions about this!

NickB
National Instruments
Applications Engineering

[j_dodek]

Hi NickB,

That's a great link! I'll give you 5!

Hi Nitin,

scrup my stuff away and follow the steps in the tutorial

it is better and much simpler!

Greetings

juergen

[goel]

Thanks NickB

this article has been a great help, actually this is what i was trying to implement.
After implementation of step mention in this article i am able to generate the link for all the failed steps in my sequence
but the only error hyperlink  which is working is the first error hyperlink rest all donot take me to the failed step.
I found that its because the #ResultID no. is missing in all the subsequent failed step.
I also tried the sequence attached in article and that worked fine although their were some version compatible issue.
Could you let me know some more detail thsi?

Regards
Nitin Goel

[nickb]

Hello Nitin,

When I downloaded the attached sequence and used it for testing purposes, the links worked flawlessly.  Were you able to use the attached sequence?  If you an error mentioning a type conflict, you can open the sequence file in your Sequence Editor, and when the type warning dialog box appears, select to use the currently loaded type.  I will check the sequence file itself for type inconsistencies, and update it's included types if necessary as soon as I get the chance.

NickB
National Instruments
Applications Engineering

[nickb]

Hello Nitin,

I see what you mean about the links not working.  I followed the steps laid out in the article myself, and the links didn't seem to work for me either.  This article appears to be somewhat out of date, and I will work to get it updated as soon as I get the opportunity.  However, I think that the sequence file that is attached to the document is configured so that the links should work.  Let me know if you have trouble using it.

NickB
National Instruments
Applications Engineering

[nickb]

sorry for so many posts, but I just had to correct myself on the last post.  The links were not working for me (and perhaps for you) because I changed the looping options on the wrong step.  The looping options should be changed on the step "Add Failure Stack Items" of the "AddReportHeader" sequence.  This is easy to miss because it's only mentioned once, at the top, of Part D.  Once I looped on the correct step, the links worked correctly.

NickB
National Instruments
Applications Engineering