RunState.Report.Append function

[richjoh]

I can't seem to get this function working here. It passes a 1 String parameter.

I want to use something like RunState.PreviousStep.Result.Status and RunState.PreviousStep.Result.ReportText to include the result of the caller sequence

[~jiggawax~]

PreviousStep does not return the Caller.  You need to to do RunState.Caller.Result.Status....HOWEVER, that will not be populated until you return to the caller so it is pointless to do it inside of the hierarchy like that.

what is your goal.  Maybe if you explain what you are going for a little better we can help you find a more viable solution.

Cheers,

[richjoh]

Goal is to report the Sequence's steps results in the sequence result list so that  indentation in the Report, horizonatal.xsl stylesheet is removed.

[~jiggawax~ · Accepted solution]

Ahhh ok.  This is a classic need/want for many people.  I'm surprised that NI hasn't built it into the default report by now.

I have a plugin that I made that ignores the indents.  Unfortunately, it is owned by my company and I can't give it away without selling it.

However, there are tricks you can do to avoid the indents.  Don't have any of the substeps report anything.  Rather, pass the data back to the caller via parameters.  Then set the sequence call step as a Multi-Numeric or Numeric step type and evaluate your limits there.  This will reduce the number of indents dramatically. 

Another option is to flatten out your result list at the end of MainSequence.  This would be a recursive function that would go through the results and flatten them.  I've attached a quick example I threw together in 5 minutes that demonstrates this.

Hopefully one of these options will work for you.

Cheers,

[richjoh]

In the "Recurse On Sequence Call" sequence, ResultList parameter is set to Locals.CurrentResult.TS.SequenceCall.ResultList <--errors on TS.Seq...

[~jiggawax~]

It will do that if you run the sequence analyzer.  Change it to:

#NoValidation(Locals.CurrentResult.TS.SequenceCall.ResultList)

This way the Sequence Analyzer won't freak out.  It will exist because of the If step before it.

[richjoh]

OK, your correct should have known its exist in RunState. I considered an error though since my Report file indentations still persist when I run Deep_Hierarchy.seq. 

[~jiggawax~]

I'm guessing you have on-the-fly on?  This will only render the report at the end of MainSequence.  If you open the file in IE after the test is complete it won't/shouldn't be indented.

[richjoh]

OK, you are correct! In Result Processing, on-the-fly reporting should be disabled for your clean up to work....

I wonder if the on-the-fly reporting has been skewing my other attempts at removing indentation. Per the Help contents :

"horizontal.xsl

Change the value of the global JavaScript variable gIndentTables from True to False in the horizontal.xsl file to disable indentation of the Sequence Call step result tables in the report."

I can never get this to work though... I'll try repeat with on-the-fly off.

[richjoh]

I noticed that on-the-fly reporting show the Sequence test result "Pass" or "Failed" but with the option disable Sequence results are not reported. Would be nice to have the Sequence Result inserted at top of step results with on-the-fly disabled.