TestStand 2017 SP1 Changes

Learn about new features, behavior changes, and other updates in TestStand 2017 SP1.

LabVIEW Run-Time Engine Error Reporting Improvements

The LabVIEW Adapter can provide detailed error information about broken VIs when used with the LabVIEW 2018 or later run-time engine. Refer to Error Reporting for Broken VIs in the LabVIEW Run-Time Engine for more information.

Use of TestStand Tools Without Activation

TestStand 2017 SP1 enables the use of several TestStand Tools without activation.

User-Editable Installer Executable Names

You can now set the installer name when you create distributions using the TestStand Deployment Utility.

Property Loader Comment Support for CSV, Excel, and Text Files

You can now use // characters to denote a comment in a CSV, Excel, or text file that the Property Loader step ignores when reading.

Note When a TestStand 2017 SP1 sequence file includes steps that contain comments and the file is opened in TestStand 2017, the comments cannot be ignored and may result in an error reading the file at runtime.

INI File Support

Saving to and reading from TestStand files that use the INI file format will be deprecated in future versions of TestStand.

You can change the file format of a TestStand file to XML or binary formats in the following ways:

  • Use the File Format Options dialog box, by selecting the File tab of the Station Options dialog box.
  • Use the General tab of the Sequence File Properties dialog box, by selecting Edit»Sequence File Properties in the Sequence Editor.
  • Use the Update Sequence Files tool, by selecting the Tools menu in the Sequence Editor.
Notice If you change a file you store in an SCC system from XML or INI to binary, you must update the SCC system to set the file type as binary. Otherwise, the SCC provider might incorrectly process the binary content of the file that appears to be white space, resulting in a corrupt file.

Change in Installer File Name

(Windows) When you build an installer in TestStand, the default name of the executable changed from setup.exe to install.exe. This behavior change may have potential impact to post-build processes that rely on the setup.exe name. To specify a different name for the executable, use the Installer name option on the Product Information page of the Installer Properties dialog box.