Can "call executable" use the "path" environment variable?

[david_jenkinson]

Hi,

It seems when using the "call executable" step type that you either need to enter the absolute path of the executable, or the absolute working directory, in the "call settings" definition of the step.  I don't seem to be able to put in a *.exe by itself in the pathname, and have the command found, even though I can enter this same command on the command line (windows 7).  Is there a way to configure this step to use the windows "path" environment variable to find the executable?

David J.

[dug9000 · Accepted solution]

You can do the following:

1) specify cmd.exe for the file pathname.

2) Specify "/c yourexe.exe" for the argument expression

This will launch a command window and tell it to run your app with the simple file name.

The reason why you can't just put yourexe.exe in the file pathname is that TestStand does its own file path resolution that is different than what the command window does. It use its search directories to resolve relative paths. So you don't have to specify an absolute path for the file pathname setting, but it does have to be relative to a TestStand search directory or the current sequence file.

Hope this helps,

-Doug