NI TestStand Idea Exchange

Post an idea

Find yourself placing a Sequence Call step and trying to determine the appropriate value to enter for a numeric parameter called "Direction"? Tired of creating sequences with numeric parameters named like the following: "Direction_0_Up_1_Down_2_Left_3_Right"?

The solution is to support the creation of variables with enumerated type within TestStand. Enums could be created as custom variables and then used as wherever a self-documenting variable is required.

Enum type creation:

As seen from a Sequence Call step to a subsequence that uses an Enum as a parameter:

It would be helpful to be able to provide a regular expression (like Labview Match Pattern) as a string value test limit. We often look for a pattern of data within a string rather than a constant.

Maybe also a regular expression function within the built in functions within TestStand expressions would be a help also. This could provide more flexibility if a user needs it. For example adding option to gain match position, and match length as well as give the option to search in reverse and ignore case.

This idea mostly goes along with this idea. I use type def all the time in LabVIEW, especially with enums. TestStand can interact with my VIs with enums, but they are handled as a number. Furthermore, if the enum gets changed, the wrong value of the enum is often used. I really like the idea of custom data type of an enum. The ultimate would be if I only had to alter the enum once (in ctl file) and TestStand would automatically update its data type. This should be the same for clusters.