exe return code

[florinn]

Hi All,

I have a question, would you please help: do I have access in Test Stand to a string return code returned by an exe launched within a "call executable" step?

Thanks,

Florin

[~jiggawax~]

Hey Florin,

You can get access to it by using the following:

RunState.Sequence.Main["Call Executable"].ExitCodeStatusAction

At least that's what I did in a simple Message Popup step.  Other than that you can not get any string returned by an executable.

Message Edited by Sam R on 02-28-2006 02:53 PM

[Yuri_IL]

1. That already does not exist in TS 3.5 -> RunState.Sequence.Main["Call Executable"].ExitCodeStatusAction

2. I think that the correct form is -> RunState

.Sequence.Main["Call Executable"].Result.Status

I suppose that ExitCodeStatusAction  ==  Result.Status

If i am not right please correct me!

Message Edited by Yuri_IL on 05-14-2006 06:09 AM

Message Edited by Yuri_IL on 05-14-2006 06:10 AM

[RayFarmer]

Hi,

RunState.Main["Call Executable"].ExitCodeStatusAction does exist, its what you set to tell the step what action to take depending on the value of the return code value. Its also dependent on the value of the WaitCondition.

Regards

Ray Farmer

[Yuri_IL]

Ray,

When I put : RunState.Main["Call Executable"].ExitCodeStatusAction at step's Expression region it's gives a mistake and more that it when I

                    wrote RunState.Main["MyCallExe"].      <-- after 'dot' I did not get any suggestions to complete it from TestStand auto- 

                    complete   system, so the TestStand does not know that thing.

                   Perhaps, that thing does not work in Expression region? If that must to work, so it does not exist in TestStand 3.5.

                   If you think that it must to work, so in which section i must put it?

Message Edited by Yuri_IL on 05-15-2006 12:47 AM

[RayFarmer]

Hi Yuir_IL,

ExitCodeStatusAction is dependant on what the WaitCondition property is set to. If the WaitCondition is set to No Wait, then maybe it doesn't give you the opposite. That is want happens when you open the Configure Exe dialog.

Regards

Ray Farmer

[Vedeja]

Florinn!

Could you post your exe so that one may try to figure it out?

/Vedeja

Message Edited by Vedeja on 05-29-2006 12:42 AM

[florinn]

Thanks guys, I do not have an example to provide, I was exploring the possibility of retrieving an exe's exit code as a string.

[Vedeja]

Well then, is it not as simple as

Str(RunState.Sequence.Main["Call Executable"].Result.ExitCode)

?

/Vedeja