08-17-2011 09:42 AM
I am fairly new to Teststand. I am just getting started on threading techniques in TestStand. Previously, task A and B were running sequentially. To improve program run time, I am splitting the tasks into thread A and thread B. In the sequential version of the program, task B is running certain steps and logging to a Teststand log file. After I split the tasks into their threads, thread B does not perform the logging feature. Before the thread split, task B would log each error using
RunState.Step.Result.ReportText feature. This logging thread is the last step before thread A and B rendezvous. How do
I enable the logging in Teststand for thread B?
08-17-2011 11:18 AM
You need to add a Wait step for the new thread. It will get added to the report if you are waiting on that thread.
08-17-2011 01:29 PM
So, this is my program structure :
1. Create Rendez-vous object
2. Split main program into Thread A and B
3. Rendez vous point for A and B
Should I modify the rendez-vous point as a wait step? Or should I add a wait statement after Rendez Vous point?
08-17-2011 06:05 PM
I'm not sure if you need the rondezvous or not without knowing your program design. It may not be neccessary. Any sequence call that calls into a new thread will need a Wait step if you want if you want it in the report. It sounds like you don't need the rendezvous without knowing any more information.