NI TestStand Idea Exchange

Community Browser
Top Authors
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

A TestStand configuration wizard

 

I would like to see a TestStand configuration wizard that would walk a developer through a checklist of all of the most important configuration settings and generate recommended changes.

 

It is best for a developer to be already familiar with Best Practices as in the following link:

 

Best Practices for Improving NI TestStand System Performance

http://zone.ni.com/devzone/cda/tut/p/id/7559

 

However, it would also be nice to have assistance in recording WHY certain choices are made as shown in this image:

17669iC6E2378DE5CA3B29

 

 

Eugene

Everyone should be familiar with the Sequences pane. In it, we get fancy icons for certain callbacks, but I'd also like each sequence reveal more information about the sequence's settings, and my first thought was to use helpful overlays for the icon. If you take a peek in the Sequence Properties dialog, you'll see there's three different tickboxes there that (can) radically change how a sequence executes. Unfortunately, I don't have any awesome ideas on how these could be presented (especially all at once) - it'd be pretty tough to fit all that discernably into a 16x16 icon. Both Comments and Requirements are visualized clearly, but I would just as soon trade the Comment column for a way to display these settings.

 

sequenceicons.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 I'd be even more thrilled if the SequenceCall step type could also find some visual way to display this information, but I guess we should probably take this a step at a time 😉

Step type: Label

Tab: Label

Field: Label Description

 

Most text field can zoom in, but not the Label Description.

It would a lot easier to read if one can ZOOM IN in the field.

 

I would like to request a change in the behavior of the Sequence Editor when dragging and dropping multiple subsequences into, for example, the Main Sequence as Sequence Call steps.

 

Currently, after dropping, the view automatically jumps to one of the dragged subsequences. A much better UX/DX would be if the view remained at the drop location instead of shifting focus to another sequence.

It would be great to be able to generate a FileGlobal or a local variable by right clicking a detected field in a Sequence step and choosing the relevant option as shown in the image below:

TomerKigel_0-1732697800669.png

That is instead of manually having to do it.

NI_Follower_0-1710508258374.png

I have created a custom type variable. Now to update the contents in this variable, without disturbing the original definiton - I need to create a container and then copy past all these variables inside. 

 

If there is a right click option to remove the custom type and make it as a container which can be then editable it will be helpful.

Hi NI Teststand developers

Don’t you find it hard setting up Teststand with all the different settings possible, scattered in al the different locations?

 

Why is it not possible to put all this settings in one form with tabs. (like in MS VisualStudio)

Especially the Cfg directory is  packet with possible stumbling rocks.
This improvement includes the configuration menu.

 

I usually spend a lot of time just setting up TS. When finally arriving in the deployment state. I stumble again trough this setting forgetting important things because they are scattered throughout Teststand.

 

It would be an immense improvement of the TS usability

 

 

If you start improving this, don’t forget to adjust the editable field sizes of forms etc., so they can be read and edited in a practical way.

 

Another thing I find not really user friendly, is the form settings lock. When I try to load a workspace and the lock is set (worked in TS2019), I get an error. Why this?

 

It would be nice to hear your statement to this,  and when you find time to improve this.
If you need more improvement hints  (there are some more) , don’t hesitate to contact me.

 

Hello all,

 

I'm starting to do some Test Stand sequences, and I'm having a Fatal Error that is always forcing me to close the program. This error always happens in the first run and I just can avoid it by deactivate and activate one option in the adapters configurations tab.

 

The error that I'm having is the next one ->  "labviewv.lib was unable to locate a suitable location to resolve "MGApp". This may happen when too many instances of labview have been loaded into the same process."

 

Can someone help me to correct this error?

My team uses Analyzer Rules to enforce best practices for developers across sequence files and workspaces with great results.  However we would love to be able to also provide rule checking and warnings for developers on some basic *.tsd file content  such as Installer Name field, and build-path & installation-path/image-path, etc...  New (or rusty!) developers often miss steps in their configuration and needlessly struggle with badly behaving deployments.

As TSD files do not appear to have an API available from TestStand at this time nor conform to  a json/xml syntax internally, for easy parsing via 3rd party tools, some method(s) for 'reading' file (or converting to readable syntax) may also be required in order to build rules effectively?

Hi,

 

it can be a simple and stupid question, but I don’t get why, when I define a container as a parameter of a sequence called in the main sequence. That parameter can’ be expanded to fill the different field with the variables that I need. I created also custom type variable for trying to achieve this aim but nothing. I thing that passing a container as parameter can be helpful in particular when you need to pass a lot of variables regarding the same “object".

 

Best Regards,

Zuc

Download All

For a mile long sequence, it would be nice to have a filter.

For example, I want to see only "Message Pop" steps, so I can eliminate/skip them to automate the sequence; or I want to skip all the subsequence calls for the first run after I made a lot of changes.

 

I know there is a distinct icon for each step type.  But for a long sequence, it's hard to catch all the steps I want to change.

Hi there,

 

When using the Find/Replace dialog in TestStand, it would be nice to have a checkbox under "Elements to Search" that allows the user to choose whether or not to include sequence file attributes in the the results. I guess I could put together a regex to accomplish what I need to, but a checkbox would be nice.

 

FindOption.png

 

Why am I asking for this?

I'm used to quickly working my way through find results by using the CTRL+G / CTRL+Shift+G shortcuts. When I hit one of these attributes there's about a 4 second delay before the sequence file attributes dialog opens. This is super annoying in the workflow of the find results, and the vast majority of the time I'm not interested in searching the ignored Sequence Analyzer messages.

 

Thanks,

 

Mr. Jim

 

IgnoredMessages.png

 

 

 

I'm working extensively with LabVIEW VIs and Test Stand, and one of the most helpful features existing is the ability to configure a TestStand type to pass its data to and from a LabVIEW Cluster.

 

I think a great way to expand upon this would be to allow the developer to override specific variables within the LabVIEW cluster.

 

For instance, say I have defined a TestStand type with 5 total variables, all of which may pass to a LabVIEW cluster. If my LabVIEW cluster has at least the same number and type of variables, then this cluster passing has no issue.

 

However, if my LabVIEW cluster has 6 variables, then the TestStand type can only account for its defined five variables, and I am effectively locked out from the sixth variable. I cannot edit the sixth variable, nor can I assign it a default value (see Ex1_broken.PNG)

 

This wouldn't cause an issue if I could override specific variables within the cluster passing. That is to say, if I were given access to that sixth variable from the example, then I could assign it to a local variable. The other five variables would still be satisfied by the TestStand type, and no errors should be generated by the step. (see Ex1_fixed.PNG for what I envision this to look like)

Download All

In our Company also hardware developer creates testsequences in teststand, so it would be nice, if there could be a small user interface to configure the values of the parameters for a subsequence.
The solution could be, if they drag and drop a sequence into their main testsequence, a user interface pops up to configure the parameters for this subsequence. So it would be possible to restrict the values with a drop down menu or Radio Buttons or to give some graphical help to choose the right values.

 

Or maybe i could create something similar to the IVI sequences, where i can click on a button and a small editor window is opened.

It will be good if a "Extract" sequence option present: When we select more than one steps in a sequence, show this option. Once you select extract option, new sequence should be created within the .seq file, and automatically insert a step "Sequence Call" which calls the new sequence.

Hi,

 

Test tand is very useful to me and always feel thanks. Nevertheless sometimes I feel that how about hide skipped steps, sequence and something like that. If there is a function of "Hide skipped step or Hide skipped all", I will obviously use them every 50 times. 🙂 

How do you think about this suggestion?

 

Thanks in advance.

TortoiseSVN is an easy to use Source Code Control tool. However, it needs a MSSCC API plugin in order to be integrated with TestStand. On NI web page, PushOK is listed as a tested plugin with TortoiseSVN by NI tech team. PushOK is made by a Russian company. Another AgentSVN plugin is made by an Australia company. From an end user perspective, the time zone difference will cause some difficulty to access tech support in case it is needed. I used TamTamSVN 1.4.9 plugin for TortoiseSVN integration with TestStand and it worked fine. TamTamSVN plugin is made by an US company located near NYC area. I will suggest NI Tech team to test TamTamSVN plugin for TortoiseSVN integration with TestStand to ensure its features and functionality are acceptable to NI applications. If it pass the test, please add it into tested list. 

For an easier debugging it would be good to have coloured lines for (nested) loops or the the possibility to hide the content on demand.

Adding Wait function i.e. you could insert a delay in case of "Looping" setting different from "none".

 

Paolo

Hi,

 

Why the edit sequence file functionality is disabled during execution?

 

I think that developers should be able to edit the sequence file in sequence editor whilst the file is executing.