NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Calling Teststand Via Cmd Line

I am trying to call teststand via cmd line and pass in the /outputToStdIO argument but it never returns anything. This is incredibly frustrating and I cant find any details of this actually worinfg as described in the online help doc here:
https://www.ni.com/docs/en-US/bundle/teststand/page/configuring-sequence-editor-and-user-interfac.ht...

The cmd I am running is as follows start /wait SeqEdit.exe -run MainSequence "C:\Users\Public\Documents\National Instruments\TestStand 2019 (32-bit)\Examples\Demos\Computer Motherboard Test\LabVIEW\Computer Motherboard Test Sequence.seq" -outputToStdIO -quit

This successfully runs the sequence and returns but I never get anything out of the -outputToStdIO argument. Is there any suggestions from anyone here? The end goal is to write a script that gets called via Jenkins

 

Thanks

0 Kudos
Message 1 of 3
(1,471 Views)

You can have a look at this repo.

https://github.com/425J/TestStandCLI

 

It requires polishing (I don't know good .NET practices so I improvised) but you can fork it and extract what you need from it.

 

I think for Jenkins it would be better because it will run completely silent (without GUI) and return some reasonable return code.

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 2 of 3
(1,415 Views)

I have done this before In TestStand 2019 32-bit.

 

My CMD was as follows. Difference being I used a C# User Interface instead of the Seq Editor. I also used Single Pass, instead of just running the MainSequence. I also passed in arguments to configure my test, but I removed them in the example below.

 

""C:\Users\Public\Documents\National Instruments\TestStand 2019 (32-bit)\UserInterfaces\Full-Featured\CSharp\Source Code\Bin\x86\release\TestExec.exe"" /operatorInterface /runEntryPoint "Single Pass" "MySequenceFile.seq" /outputToStdIO /quit

 

If I had to take a guess, I would imagine if you use an entry point vs just running a sequence you may get something.

0 Kudos
Message 3 of 3
(1,394 Views)