Archived:Convert LabVIEW or LabWindows™/CVI™ Test Executive Toolkit Sequence to a TestStand Sequence

Updated Apr 14, 2023

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.



  • LabWindows/CVI Test Executive Toolkit
  • LabVIEW Test Executive
  • LabVIEW Test Executive (Legacy)
  • TestStand

I would like to move from using the LabVIEW or LabWindows/CVI Test Executive Toolkits to using TestStand. Can I migrate or convert my Test Executive Toolkit sequences to TestStand sequences?

TestStand includes two tools for converting Test Executive Toolkit sequences to TestStand sequences.  In TestStand 2010 SP1 and previous, these tools are located in the Tools menu of the TestStand Sequence Editor. TestStand 2010 SP1 is the last version of TestStand to include the LabVIEW and LabWindows/CVI Converters in the TestStand installer.

Converting to TestStand 2010 SP1 and Previous Versions
To convert a Test Executive Toolkit sequence to a TestStand sequence for TestStand versions 2010 SP1 and earlier, open the TestStand Sequence Editor, and navigate to Tools»Sequence File Converters»Convert LabVIEW Test Executive Sequence... or Tools»Sequence File Converters»Convert CVI Test Executive Sequence... depending on the type of Test Executive Toolkit sequence you are converting.

Note: In order to successfully convert LabVIEW Test Executive sequences using the LabVIEW converter, the active version of LabVIEW must be between 8.2.1 and 8.6.1. Additionally, after running the LabVIEW converter, you must open the auto-generated TestStand sequence file and run the Update VI Calls  tool to ensure that the LabVIEW steps in the TestStand sequence file are correctly configured and up to date.

Converting to Newer TestStand Versions
In order to convert to a newer version of TestStand than 2010 SP1, use an older version of TestStand (2010 SP1 or previous) to convert to a TestStand sequence file, then upgrade the TestStand sequence file to the newer version of TestStand using the migration utility.