11-22-2005 10:12 AM
11-22-2005 11:18 AM
11-22-2005 11:35 AM
Thanks for your comments. We use TestStand databasing for our record access, but could look at modifying the text file sequence shipped with TestStand. Enclosed is a sample file I 've created for reference. Looks simple enough but is a difficult situation considering the number or parameters, and subparameters necessary to pull out of TestStand.
To pull from TestStand, I suspect I need to programmatically obtain # Steps, Step Name, and all subparameters down the line.
Icing on the cake is the CM has this in an TestStand OI and refuse to provide to us.
Thanks again.
11-22-2005 12:28 PM
That actually looks similar to what I had to do for one CM. The existing report_gen.seq already gets this information. Some of the text is formatted in a DLL but you can replace that. For example, the sequence called PutOneResultInReport creates a string called Locals.ReportEntry. If you look at how this string is built, you'll see how it gets step name, etc. and then adds a \n at the end for a new line. Instead of the \n, you can add the "|" character that's in your example.
11-22-2005 12:34 PM
Looks like the way to go. Alternatively, I could pull this into my main sequence as a final step sub or in cleanup, and call it there (as long as variables are initialized properly).
Thanks again Dennis.
11-22-2005 12:52 PM