Hide TestStand Sequence Editor Interface to Operators

Updated Nov 8, 2018

Reported In


  • TestStand

Issue Details

  • I am developing a test sequence with TestStand, which I will deploy to a testing facility. Nevertheless, I don't want the operators to have all the Sequence editor functionality, since they could alter the problem. Moreover, I do not see the need of having the sophisticated user interface for them. How can I hide it?
  • When we deliver this to production, we would like to automatically load the sequence, and not have a first dialog that comes up for credentials and whatnot.


The <TestStand>\UserInterfaces directory includes the subdirectories that contain the executable, project, and source code files for example user interfaces, which do not give the full functionality of the Sequence Editor. Instead, they show a useful environment in which operators can load, execute and terminate the tests without being able to modify them. Learn more about TestStand User Interfaces here: Creating Custom User Interfaces


Moreover, these user interfaces can be fully customized using LabVIEW, LabWindows™/CVI, and C#, etc. to fit your needs and adapt to the test your operators are running. Learn more about them here: Example User Interfaces

Additional Information

TestStand includes simple user interface examples that demonstrate the concepts of TestStand user interface development. You can also use these examples as a basis for creating your own custom user interfaces. These examples demonstrate the following basic TestStand functionality:


  • Opening and executing sequence files
  • Viewing the status of running executions
  • Breaking and terminating executions
  • Viewing reports for completed executions


Not Helpful