Loading test steps during execution

[Gops]

Hello,

I am using the operator interface from the example. I have modified to suit my application. I run the test using the Single Pass entry point. I have 46 steps in my main sequence. When I press the Single pass execution, Initially it takes a lot of time (I think it compiles all the steps) to start the actual execution.

Why does it take long time to start execution? Is it possible to configure test stand such that it compiles each step as and when it reaches it?

Regards

Gopal

[RayFarmer]

Hi,

What TestStand version are you using and what language are your code modules in?

TestStand doesn't compile anything but it could be loading your code modules if you have set the steps to load dynmanically.

What modifications have you dont, if you use the default OI does this take the same length of time.

Regards

Ray Farmer

[Gops]

Hi,

I am using Teststand 3.5. My code module are in Labview. I use the OI of labview.

It takes same amount of time in the default OI also.

My main sequence consists of 46 test steps. Each step calls a sequence. I have configured each step in the main seq to run in a new execution with Single Pass entry point and wait for execution to complete before starting next step.

Regards
Gopal

[AndrewMc]

Hey Gopal,

As Ray said, TestStand does not actually compile your modules.  That being said, most likely this load time that you're seeing at the beginning of execution is due to your load options set to load the module when execution begins.  If you go to the step properties, notice under "Run Options" there's a "Load Option" drop-down.  You can look at the help for a description of this property, but in general this setting refers to when the module is loaded into memory.  For time-critical tests, you would want to load either at the beginning of execution or when the sequence file is loaded (as this would extract the load time from the step so that the step could be executed quickly); this is especially important if you are looping on a particular step.  There is an option to "Load dynamically" as well.  With this option, you would see a slight delay before each step during which its module is loaded - rather than a longer delay at the beginning (in which all step modules are loaded).

Note that the default is "Preload when execution begins"; that is why I'm guessing that this is responsible for the delay that you're seeing.