Failed Test Steps reported multiple times in Report

[GSinMN]

Running Multiple Numeric Limit Tests in a for loop, and when a test step fails, the result is reoprted multiple times in the report (sometimes repeated as many as 5 times for one failure).  Thought it had something to do with the fact that it was a multiple numeric limit test, but each test only checks 2 limits.  Also, sometimes the result appears indented in the report, almost like TestStand thinks it is starting a new section, in the middle of a test.  Any ideas?  Please advise.

Thanks,

GSinMN   

[sahanaU]

Hi,

Which TestStand version and Report Format are you using? Please share the test sequence file if possible.

I executed the attached sequence file which has Multiple Numeric Limit Test with 2 limits in a for loop  and generated ATML 5.0 report using tr5_horizontal stylesheet to display. The results appeared as expected in the report with failures shown for each iteration in the loop.

 

Regards,

Sahana

[GSinMN]

Hello Sahana,

 Unable to share sequence or report directly.  Proprietary info.  Running TestStand 2013, Format is plain HTML.  Same behavior started for passed tests now as well.  

  I've been testing a few changes and may have gotten close to fiding the issue. It seems that it is related to editing the expression in the "Result Filtering Expression" box.  For Example, there is a built in option for showing passed or done only, with the expression reading Results.Status == “Passed” || Results.Status == “Done”.  If I change this to read Results.Status == “Passed” || Results.Status == “Failed”, it appears that this is when the odd behavior occurs. Should I not be allowed to change this field?  Thinking there may be an issue in the sequence that generates the report that can not handle this customization reliably.  Anyone have any thoughts on this?  Thanks.

GSinMN 

[LindsW]

Hi.

Based on the help documentation for the Result Filtering Expression here, you should be able to use any subproperty you want in the expression.

I do want to clarify - you should be using Result.Status not Results.Status in this expression. Is this what you are doing?

Also, would it be possible to post a screenshot of the part of the report that is behaving this way. Perhaps you could black out the parts of the report that you cannot share.

Regards,