How to pass a command line argument to the sequence?

[AlanJ]

Hi,

My GUI is written in VB.NET. I can read the command line argument in the GUI, using: Me.AxApplicationMgr.CommandLineArguments(). But I don't know how to pass it on to my sequence file which the GUI invokes. How do I read the command line argument from the sequence file?

My purpose, is to have the same basic sequence execute different subsequences depending on starting conditions...

I am using TestStand 3.0 with a VB.NET GUI, on Windows XP.

I'd appreciate any help on the subject.

Alan

[RayFarmer]

Hi Alan,

One obvious way would be to add parameter(s) to the MainSequence and then modify the process model sequence file to use the new parameter(s) in the step "MainSequence Callback"  in either Single Pass or Test UUTs but I wouldn't recommend this approach.

The sequence file to be run via the entry point can be found at "RunState.ProcessModelClient" and the lookup string to the MainSequence would be "RunState.ProcessModelClient.Data.Seq["MainSequence"] or .Seq[0] .

Therefore you could quite easy use the SetVal method to setup a Local variable in the MainSequence of your Sequence File to receive the command line string.

Also you could do this without altering the Process Model Sequence File by using the Callback Sequence ProcessSetup in your Sequence File.

As an example.

You have a string in your Locals of MainSequence called CmdLineStr.

If you add the Callback Sequence ProcessSetup to your SequenceFile, then add an ActiveX Automation Adapter step which is setup for a PropertyObject and the reference is RunState.Caller.RunState.ProcessModel.Data.Seq[0].Locals.CmdLineStr.

There is an extra RunState.Caller to the lookup string, that's because I am doing the work in a SubSequence of Entry Point Sequence.

The method to use is SetValString and the parameters of the PropertyObject will be

lookupString = ""

options = 0 or 1

newValue = where evey you have stored you command line string.

Now when you run your sequence file you will find that the Locals.CmdLineStr will contain your parameter string.

Hope this is of help to you.

Regards

Ray Farmer

[AlanJ]

I got a solution: I wasn't able to write and then read a Local variable. But I am able to write and then read a FileGlobals variable. I'd speculate that this might be a TestStand version 3.0 limitation...

Thanks for your help,

Alan