It would be nice to be able to create a new sequence from highlighting steps in a sequence and performing a right mouse click, "Create New Sequence...", this would be a kin to Create SubVI in LabVIEW.
This action could display a dialog to give possible options such as, to copy the Setup and/or Cleanup group, Create in a New SequenceFile or in Current SequenceFile, the option to Move or Copy highlighted Steps. It could also include creating any locals and /or FileGlobals (if creating in a new SequenceFile) used by those highlight steps.
It would be helpful to be able to change the font colors that are displayed for steps in the sequence editor. This would allow users to identify steps quicker for more efficient editing and debugging.
Hello all TestStand fans,
For my recent project i had to modify the frontEnd callback.
=> According to the TestStand help, the only path where this file can be created is in TestStand default path or in the corresponding user path.
.... But no where else !!!!
It would be nice to be abble to configure the frontEndCallback path in the configure options !
=> Doing so, the path of this callback could be placed everywhere ! (In the configuration path would be nice !)
=> Doing so, it would be possible to create a frontendcallback for each configuration !
I am a TestStand developper, a NI partner, not a TestStand end user.
My work is to provide custom sequencer for my customer.
On my computer i had to manage many different sequencer !
I think that if it is impossible to do so, today, is because this callback is loaded before the "Station configuration" is loaded ?
My ideas should be applyed to all global files ...
Doing so, will also simplify the deployement process !!!!
=> A single path copy ... is quite easyer as a complicate deployment process !
Thanks for your help.
Within the Teststand workspace it would be reall useful if the "Code Modules" under the sequence could auto-populate and also if it could display the filepath of the code module. That would make it much easier to keep track of what code a sequence is calling and where from on disk.
I think this Thread should be placed here.
The aim of this is that users can create the same powerful steps like that once which comes from NI.
Biggest enhancement of this would be that i can get rid of the "edit" - button and there is no floating panel
The second enhancement is that i may use drag and drop between the edit and variable panel (if this is neccessary).
Like Manooch_H I am interrested in comments, too
It would be nice to beable to define a variable as constant.This could apply to Locals, FileGlobals, StationGlobals.
Once set mark it so as to be easily identifible as a Const.
The API would also need to include either a Property or Method so that one could determine if a variable is a Constant.
How many of you would benefit from the addition of a feature similar to LabVIEW's Quick Drop?
The functionality that initially comes to mind would be typing to search for your desired step type or step template and dropping it into the sequence you are developing. Please add comments for any additional functionality you might like to see in a TestStand step Quick Drop (for example, you may want TestStand to automatically navigate to the Step Properties of a step after it is dropped from Quick Drop).
Please also add comments for any other situations/scenarios (outside of adding steps to a sequence) where you might benefit from a Quick Drop-like functionality. Thank you.
When you set the Post Action On Pass | On Fail in a step to use Call sequence, the only ways to pass data to this sequence is either use some sort of Global (StationGlobals / FileGlobals) or use Locals with the setting "Propagate to SubSequence".
There should be a cleaner way and that is to beable to pass parameters as you do with SequenceCall step type.
It looks like there is no "gentle" way to access the results of the executed tests in ongoing execution during this execution.
Sometimes there is a need to access the test results during the execution, before the data will be committed to the database, and execution is still ongoing. The reason for that could be we can reuse the some data of the test in other tests, or we can use for example the status of the test to drive the flow in our sequence.
It looks like there is no other general way to do that as only described by Sasha here: http://forums.ni.com/t5/NI-TestStand/RunState-Proc
So, theoretically, - please read Sasha post - we have recipe to access all results we want. However, problem with accessing the result list is that, that it is done via the index of the ResultList array.
It leads us to two problems:
1. the elements in that list depends on the step position in the sequence file, which makes the editing sequence almost impossible,
2. if our sequence contain loops the problem from the point above is even more impossible.
Therefore, the idea:
Please prepare the easy accessible, not index based as it is now, method (container?) which developers can access the Results containers of the steps on the fly during the execution.
Handler proposal 1:
Step name (binded as unique ID) + execution order number
Handler proposal 2:
Callers path + StepName +execution order number
where execution order number could be the handler which could be number 0 by default unless the step is called few times.
Exactly as in the subject.
Sometimes the names variables are long and could be deeply nested into containers.
Now it is difficult to use them as both windows: the main one and Selected are unresizable.
After proposed change the property loader would have all default features(behaviours) as you can expect from the window at this place.
Current situation presented on the picrure below.
Having the ability to have line numbers for all steps in the left hand gutter would help in troubleshooting, code reviews, and any time when communicating about a sequence. There seems to be a gutter there already, so adding there seems to be a place for them already. Error messages can also post the line number too.
During development of sequences I often do "trivial" changes in order to check parts of the sequence that I do not want to save afterwards (e.g set Run Modes of steps to Skip). It would be very helpful to see the last changes that can be undone before clicking the Undo-Button arrow (the same applies for the Redo Button of course). This feature would have two major advantages, since one could...
This is implemeted in Microsoft Office programs for example (see screenshot from MS Excel) and I use it there pretty often.
Hello all TestStand users,
How often i had to debug my sequences ... to find out after many minutes that some of my steps are Skipped !
It would be nice to highlight the skipped steps by default ... (Without having to customize something in TestStand)
Thanks for your help ...
It would be nice when entering in the Find: control to beable to pop open the Variable dialog (as in the expression editor) to select variable names. It could be linked to the Limit Search to: control. Like wise on the Replace control when that window appears.
I know you have that drop down facility on this control but that only remembers what you have previously entered.
The menu to create a new variable (right click on variable in an expression edit control and select Create "VariableName") contains all the data types you can use for the variable, however, in the LabVIEW Panel (and other similar panels or dialogs) there is enough context information about the variable to suggest a data type, for example, if the variable is in a control of type Double we know we should create a Numeric variable. TestStand should add the contextual suggestions to the top of the context menu and bold them so that I can more quickly select the data type I want most of the times, then have a separator and put the normal menu so if I don't want that data type for some reason I can still choose the other data types (see attached image).
If you have lot of code between an if, else, end statement steps (and other flow control structures for, foreach, while, and etc.), it would be nice to roll all that up so you can see more of the flow of the sequence. This will also help to know what steps are in those structures in large sequences. TestStand already has some code folding in the sequence, so this is an expansion of this. Many text and code editors have this feature and it would be a great feature for TestStand.
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.