result filter behavior differerent in ATML vs HTML

[Frank_L.]

Hi David,

I've taken a look at the files you sent in and can see the behavior you're describing. I will continue researching this and will post on here when I have new information for you.

[Al.B]

Hi David,

This is actually expected behavior, and it is due to the way the report file is structured in XML formats (ATML and XML).  The sequence results are stored in a hierarchy such that the results for steps in a subsequence are stored within the results for the calling sequence call step, as seen in this simplified excerpt from an XML report (in this case, mainsequence calls a subsequence containing a pass/fail step):

<tr:ResultSet ID="7" name = "Unsaved Sequence File#MainSequence">
		<tr:TestGroup name="Unsaved Sequence File#Sequence" ID="8" callerName='SequenceCall'>
			<tr:Extension>
				<ts:TSStepProperties>
					<ts:StepType>SequenceCall</ts:StepType>
				</ts:TSStepProperties>
			</tr:Extension>
			<tr:Test ID = "9" name = "Pass/Fail Test">
				<tr:Extension>
					<ts:TSStepProperties>
						<ts:StepType>PassFailTest</ts:StepType>
					</ts:TSStepProperties>
				</tr:Extension>
				<tr:Outcome value = "Failed" />
			</tr:Test>
		</tr:TestGroup>
	</tr:ResultSet>

 You can see that the results for the pass/fail step are stored within the results object for the sequence call step.  For this reason, if the sequence call step does not get logged, neither does any of the step information for the called subsequence.

TestStand R&D is aware of this behavior, and we plan to better document it in a future version of TestStand.  At this time, there are two possible approaches to get the behavior you are looking for:

1. modify the result filtering expression so that it does not apply to sequence call steps.  you can do this by appending the following to your result filtering expression:
   
   || Result.TS.StepType == "SequenceCall"
   
   
2. Instead of using a result filtering expression, add conditional statements to the XML stylesheets to only display results with a certain status.  For information on modifying TestStand stylesheets, refer to KnowledgeBase 4SB7G6CK: Customizing the Formatting and Appearance of TestStand XML and ATML Reports.  You can also combine this with method 1 in order to remove the extra sequence call step results from the displayed report.
3. Use a non-XML format to generate the report, such as HTML

Hopefully this clarifies things for you!