test report missing info

[Sir_Mutt]

I have an odd anomoly with a text report.  I modified ReportGen_txt.seq to not print the "Begin Sequence" and "(C:\...)".  This worked fine when I had a single sequence run.  When I had two sequences run (both with generic tests) the second test results didn't populate properly.  It showed the second test result failed, but didn't give any more info.

To remove the Begin Sequence part of the report, I just skipeed the Add Sequence Name function.  If I include that step, the report generates properly.  If I keep that step included, but add a pass/fail step prior to the string step that I had included, it also generates the report properly. 

Here are screen shots to better explain the issue.  Looks like some sort of bug to me because it works fine unless the only step in Test2 is a string comparison (could be other issues, but that just happens to be what I threw in as generic tests).

[Kracken]

Hi Sir Mutt,

There is a precondition on the Remove Empty Sequence Results step that causes it to only run under certain conditions to remove empty results.  When you skip the step/steps you are skipping, it is causing that precondition to be met when it shouldn't be.  You can either skip the Remove Empty Sequence Results step, or change the precondition as shown below.  I wasn't able to find a case where it would run that step, so I'm not sure what results it is intended to remove, but I think subtracting 1 instead of 2 will keep its intended use case intact.

Regards,

Brandon V.

Applications Engineering

National Instruments

www.ni.com/support

[Sir_Mutt]

Thanks Much Kracken...  My work around was to just add a space in the Add Sequence Name step.  Your fixed worked so going with that fix.

[Sir_Mutt]

Well, I spoke to soon earlier.  With the fix described, I get an error if I run a step that only has a function call.  I should probably check to not include in the report, but if a developer does something like this and forgets to indicate not to include, I don't want to have this error thrown as it would be a mystery error to them most likely and hard to find.  Going to revert to keeping a space in the Sequence Name step.  Doesn't really change the report and gets around this issue.

See attached for error I got with this fix...