07-04-2005 10:12 AM
07-05-2005 08:00 AM
07-08-2005 02:28 AM - edited 07-08-2005 02:28 AM
All done now - works great with either cached or on-the-fly reporting. Got there in the end, after stepping through and working out the convoluted way in which the standard reporting functions put the subsequence names into the report. I'm still recovering.
I assume from the lack of reply that nobody else has done this.
Message Edited by Sean on 07-08-2005 08:28 AM
07-19-2005 03:55 PM
Sean -
I do not recommend adding to the CommonResults to achieve this. There are two types of logging as you mention: post UUT and On-the-fly. For processing results post UUT, you typically recurse through the results by process the parent result before you process its child results. The parent result is a sequence call step result and it has the knowledge of which sequence and file generated the child result. For processing On-the-fly, the PostStepResultCallback has a context. The step for the result calls this sequence. So from this context you can access the calling sequence with NameOf(RunState.Caller.RunState.Sequence) and file with NameOf(RunState.Caller.RunState.SequenceFile).