I've been working on a design which is based on the parallel process model. I need to test 4 UUTs concurrently, with each test port running the same set of tests asynchronously. For each phase of the testing performed on these UUTs I have created a subsequence. I've opted to launch each subsequence as a new execution so that I get a unique test report for each, and utilize the Sequential model and the Single Pass entry pointin these subsequences. So far, so good, I think. (I use the phrase "I think" since I'm not 100% sure that launching the subsequence as a new execution which uses the sequential model from a parent parallel model sequence is best practice. So I invite any commentary on that point as well.)
My challenge is that I'd like the test reports generated from each of these subsequence calls to reflect the socket from which it was initiated. Passing parameters to the new execution, including the current socket index from the main sequence, isn't a problem. Short of utilizing model callbacks to tailor the subsequence's report header to include the socket information, is there a better way to get the socket information to appear in the subsequence's report header? Attempts, for example, to just set RunState.TestSockets.MyIndex in the subsequence based on the socket index I passed in, don't work and result in runtime errors. I suspect this is due to the use of the Sequential model for my subsequences?
I am also logging results to a database, so I'd also like an indication of parent test socket to somehow make it into the results TS is committing to the database. Currently the database shows a socket of -1 for all subsequences launched as a new execution, regardless of the actual parent parallel socket index (0..3).
Thanks!
Jim
