NI TestStand Idea Exchange

About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Smarter Sequence file converter ...



I had recentlty to modify the public interface of one of my custom step.

The automatic type conflict detection diden't work ! I had to modify all my sequence file manually, by only launch the "reload prototype" !

(All versions of my custom step has been upgraded in order to generate a conflict !)

So, i thaught, i could use the "sequence file converter tool" to upgrade existing sequence files ...


But no ! 


The sequence file converter only converts the properties which cannot be modified by the final user. (The one who write sequences)

=> The NI Answer is : All properties that could be modified on a step instance, will not be upgraded by the sequence file converter.

So, neither the default action will never be upgraded, nor all properties ....


AIEEEEEEEEEEEEEEEEE ! :smileyfrustrated: What can i do for my customer hundred of sequenceFiles .... :smileysad:


So, I had customized my custom step in order to lock all properties for the end user (Disable properties) ...

I thaught the Sequence file converter will detect that the step instances could not be modified ... and then it will do the right work !

Even with this lock, the sequence converter don't upgrade my existing sequences !


The NI answer to my problem is : You should do it right from the begining !

It is well known that the projects need didn't change during the software life cycle !!!!!!


So i decide to do my own sequence file converter for my application ... and it works fine ... but i think this need is general ... and could be integrated into TestStand.


I would like, in the sequenceFileConverter, to be abble to :


  1. Select a path which contains recursively many sequences
  2. Select a or multiple CustomSteps to upgrade
  3. And launch an automatic "Force upgrade"


The tool could ask other options like ...


  • Keep properties or apply default
  • Updgrade action interface or not
  • keep existing parameters, and initialize default parameters with default values
  • Apply default parameters


I know very well that the behaviour of such a tool would need many parameters in order to handle all needs.

But, this could be done in many times ...


The first need is something like an automatic prototype reload, with existing parameters reusing, and default values for type mismatch, or new parameters.


Thanks for help.