From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

TestStand 2022 Q4 Known Issues

Overview

This document contains the TestStand known issues that were discovered before and since the release of TestStand 2022 Q4. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.

Bug Number

Legacy ID

Description

Details

1127168, 1127169

The transparency mask in the new icons is not set or it is not correct

The new TestStand icons do not have their transparency information set correctly. Since the transparent color is not blended properly with the background, the icons look distorted when display in some controls like buttons.




Workaround:

There is currently no known workaround for this issue. You could use custom icons. 

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

Aug 9, 2021

1225861

TestStand throws error -17301 'Index out of range' with On-The-Fly Reporting and excluding Pass/Done results

With the ATML report format, when you set the result processing options to use On-The-Fly reporting and set the result filtering expression to either Passed/Done Only or Exclude Passed/Done/Skipped, TestStand execution encounters error -17301; Index out of range.

When you set the result filtering expression to Exclude Passed/Done/Skipped, this issue occurs when a subsequence is called and none of the steps in the subsequence fail.

When you set the result filtering expression to Passed/Done Only, this issue occurs when a subsequence is called regardless of the execution status of the steps in the subsequence.

Workaround:

Use HTML or ASCII report format.

Reported Version:

TestStand: 2019

Resolved Version:

N/A

Added:

Oct 11, 2021

1440450

TestStand silently crashes when generating a test report for a large amount of data

When executing a test that generates a large amount of report data, TestStand may silently crash if you terminate the test after a significant amount of report data has been generated.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

Oct 11, 2021

1370979

TestStand Report displays different variant of graph the first time

When running a sequence that produces graphs with multiple Y coordinates, the execution report does not show the correct variant of the graphs. The specific data set to be the X index will be shown as the first Y value rather than the X index.

Note: TestStand can display multiple variations of graphs. Refer to the help document here.

Workaround:

Refresh the report by clicking the Refresh button.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

May 31, 2022

1530687

Execution report information for Sweep loop records do not match with the runtime values for capture value parameter

If a Sweep Loop step contains a parameter configured as a Capture Value parameter (Use Existing parameter prior to TestStand 2021), and a step within the Sweep Loop modifies the variable associated with the parameter, the updated value for this parameter is not reported in the execution report.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2019

Resolved Version:

N/A

Added:

Oct 11, 2021

1465511

LabVIEW user interface hangs when trying to delete a step using the Delete key

The LabVIEW user interface hangs when a selected step is deleted by pressing the Delete key on the keyboard.

Workaround:

Right-click the step and select Delete from the context menu.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

May 31, 2022

1913434

Wrong version number of LabVIEW project library created with the TestStand Deployment Utility

In the TestStand Deployment Utility, if you select the option to automatically create a LabVIEW project library (.lvlibp) with your code modules, the version number of the library will always be 1.0.0.0 instead of what you configured (a specific version number or the project version).

Workaround:

Create the installer or the image again without changing anything, and the LabVIEW project library will have the correct version number.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

May 31, 2022

1865161

TestStand Generic Insert (NI) database schema is filling Microsoft SQL database string entries with blanks

When logging results to a Microsoft SQL Server using the Generic Insert (NI) schema in the TestStand database logging tool, TestStand fills each BSTR string entry with trailing blanks up to the varchar length of each entry.

Workaround:

Create a copy of the Generic Insert (NI) schema and for each column/parameter where the Type is String (BSTR), change the value to String (VarChar).


Reported Version:

TestStand: 2021

Resolved Version:

N/A

Added:

N/A

1945884

TestStand Deployment Utility cannot locate code modules when trying to deploy a workspace with TestStand environment specified

When trying to deploy a TestStand workspace where a TestStand environment is specified, the TestStand Deployment Utility displays an error stating that it cannot find the code modules in the workspace. This occurs when code modules are not saved in the same folder or a subfolder of the workspace file.

Workaround:

Save all the code modules in the same folder or a subfolder of the workspace file.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

Nov 8, 2022

2142192

The Jedi package makes the Python step slow to display module details when a large number of Python modules are installed

When the Jedi package is installed, Python steps can respond slowly at edit time when users interact with the different step setting controls that collect data from the configured Python module. This slowness occurs when there are a large number of Python packages installed, resulting in a large number of Python modules for Jedi to access or parse.

Workaround:

Uninstall the Jedi package so TestStand does not use the new parser.

Reported Version:

TestStand: 2022 Q4

Resolved Version:

N/A

Added:

N/A

2145006

Monospace expression font not used for every display of expressions

Expression controls use proportional fonts by default which makes <issue description>

    Workaround:

    On machines where Lucida Sans Typewriter is installed, the expression editor uses that font to display text in the expression editor. When the font is absent, the expression editor uses the default TestStand font. One method for obtaining Lucida Sans Typewriter is to install Microsoft Office applications on the machine.

    Reported Version:

    N/A

    Resolved Version:

    N/A

    Added:

    N/A

    1274455

    LabVIEW fails to open help for TestStand API property nodes in machines with Windows 10 (build 20H2) and above

    When trying to open help for TestStand API property nodes in LabVIEW, the content does not open either in a web browser or in the hh.exe application.

    Workaround:

    Manually open the TSAPIRef.chm file from <TestStand>\Doc\Help.

    Reported Version:

    TestStand: 2019

    Resolved Version:

    N/A

    Added:

    N/A

    2186839

    Error occurs when trying to create a deployment that uses an environment file

    When trying to create a deployment that use an environment file, error -18360 occurs, stating that changing environments requires the ConfigEngine privilege. This happens when outside of TSDU, the Engine.StationOptions.RequireUserLogin = TRUE and ApplicationMgr.LoginOnStart = FALSE API calls are executed before the deployment is attempted.

    Workaround:

    Do not have the Engine.StationOptions.RequireUserLogin = TRUE and ApplicationMgr.LoginOnStart = FALSE API calls executed in the system in which you are attempting to create the deployment through TSDU.

    Reported Version:

    TestStand: 2020

    Resolved Version:

    N/A

    Added:

    N/A

    2187010

    The LabVIEW adapter truncates the namespace of VI when its full path is longer than MAXPATH

    The LabVIEW adapter incorrectly truncates the namespace of the VI when the length of the VI's path plus the namespace is longer than MAXPATH.

    Workaround:

    Place VIs in shorter directory paths.

    Reported Version:

    N/A

    Resolved Version:

    N/A

    Added:

    N/A

    2221191

    Images in column headers are not displayed

    Images in the column headers are not displayed. This affects those column headers that have an image, e.g., Level and Write to Output Stream in the Sweep Loop step, or Include in Report, Is Measurement, and Is Limit in Additional Results.

    Workaround:

    There is currently no known workaround for this issue.

    Reported Version:

    TestStand: 2022 Q4

    Resolved Version:

    N/A

    Added:

    N/A

    Final Time Issue Listed

    Issues found in this section will not be listed in future known issues documents for this product.

    Bug Number

    Legacy ID

    Description

    Details

    1917376

    Message Popup step is unable to display an XML file

    When a Message Popup step is configured to display an XML file that uses an XSL stylesheet, and the XML file refers to the XSL file using a relative path, TestStand returns an error stating that the stylesheet path could not be found even though the stylesheet exists on disk.

    Workaround:

    Use an absolute path in the XML file to refer to the XSL file.

    Reported Version:

    TestStand: 2021 SP1

    Resolved Version:

    N/A

    Added:

    May 31, 2022

    1915574

    Stepping into a Python code module sometimes puts Visual Studio Code into a waiting state

    When Visual Studio Code is out of focus, and you step into a Python code module, then click on VS Code from the Taskbar, VS Code is not responsive and does not add the intended breakpoint to the Python code module.

    Workaround:

    Click anywhere outside of VS Code to take focus off the application, then click within the VS Code window to return focus.

    Reported Version:

    TestStand: 2021 SP1

    Resolved Version:

    N/A

    Added:

    May 31, 2022

    1915779

    Unable to step into a Python code module with Visual Studio Code when the breakpoint was removed during an earlier debug session

    In a debugging session, if you remove a breakpoint to a function in a Python code module, and if you intend a Python step to step into this breakpoint later in the execution of TestStand, the step into action does not break on this function in the Python code module. This happens when, prior to this debug session, you stepped into this Python function in Visual Studio Code, then closed VS Code without stepping out of the Python code to return to TestStand.

      Workaround:

      There is currently no known workaround for this issue.

      Reported Version:

      TestStand: 2021 SP1

      Resolved Version:

      N/A

      Added:

      May 31, 2022

      Additional Resources

      Explore Support Content and Product Documentation 

       

       

      Ask the NI Community

       

       

      Request Support from an Engineer

       

      A valid service agreement may be required, and support options vary by country

       

      Glossary of Terms

       

      • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
      • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
      • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
      • Workaround - Possible ways to work around the problem.
      • Reported Version - The earliest version in which the issue was reported.
      • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
      • Date Added - The date the issue was added to the document (not the reported date).