12-18-2017 10:52 AM
It is not possible to evaluate a Multiple Numeric Limit Test when using new thread. Look at example Threads
I have made a workaround but it looks not like good code. Look at Threads Workaround
Is there a better way?
12-19-2017 09:45 AM
12-19-2017 10:09 AM
Thanks for your reply.
I am using TestStand 2014 sp1.
When using Threads.seq it evaluates on the default value instead of the value returned in parameters. How can I evaluate on the returned parameter when calling a new thread?
12-20-2017 02:37 AM
12-21-2017 04:48 AM
Hey,
So the reason it isn't working in TS 2014 is that the output parameters for the steps aren't populated until the very end. This has been modified in the behaviour for 2016. Unfortunately there isn't an easy was around this, apart from the method you've already looked at. You'll need to save the values to another location and call them back when using the limit test.
You should notice that even though it fails the test and uses the default values, the step populates it's results with the values you've set in the statement step.
While the workaround you have may not look the cleanest, if you aren't going to be updating to 2016 it might be the option you'll need to use.
Thanks,
Nic
04-20-2021 05:16 AM
Good Morning,
Do you have ever performed the parallel execution of that different threads? Because in a serial execution I need at a certain step, to start 8 sequences at the same time (I think that this is like creating a fork), each one performing its actions.
Is it possible in TestStand? Do you have any suggestions?
Thank you for the help!
Best Regards