08-06-2003 05:39 AM
08-06-2003 06:33 AM
08-06-2003 08:49 PM
08-07-2003 02:47 AM
05-18-2012 12:21 PM
So this thread is ancient, but I still found it helpful. It was also useful to know that you can use the Step.StepIndex parameter instead of hardcoding the index to the subsequence you're calling, like so:
RunState.SequenceFile.Data.Seq[Step.StepIndex].Requirements.Links[0]
I'm using this to customize the TestStand report to include the requirement property listed under that subsequence.
05-18-2012 01:45 PM
Correction, using Step.StepIndex as in my above post doesn't make any sense, it was only working by coincidence. The following is what I wanted, using the name of the callee as the index:
RunState.SequenceFile.Data.Seq[Step.Module.SeqName].Requirements.Links[0]