Home Support Documentation Bugs

TestStand 2021 SP1 Known Issues

Created Jun 22, 2023

Overview

This document contains the TestStand known issues that were discovered before and since the release of TestStand 2021 SP1. 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.

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 displayed 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:

N/A
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
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:

N/A
1877776

Reports generated by the Sequence Analyzer use default rules instead of rules you specify

When you make changes to the Sequence Analyzer rules and then click Generate Analysis Report, the report uses the default rules and the changes made to the rules are not reflected.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

N/A
1897783

The Home button on the report view control does not move the page to the beginning

When you click the Home button in the report view, the report does not reposition to the beginning.

Workaround:

Press the Home key on the keyboard.

Reported Version:

TestStand: 2021 SP1

Resolved Version:

N/A

Added:

N/A
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:

N/A
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:

    N/A
    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:

    N/A
    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:

    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
    1140359

    Unable to enter parameter value in the Value expression control in some full-featured Editor UIs

    When you configure a step to use the Python or LabVIEW NXG adapter, then select a module for the step, the Value expression control in the Parameters Table freezes sometimes. When this occurs, you cannot type in it or use the Expression Browser Dialog Box to enter a value.

    This issue occurs in the C++, LabVIEW, and VB.Net full-featured Editor UIs.

    Workaround:

    Workarounds:
    1. Press the <Ctrl> key once.
    2. Force refresh the dialog by going to another application and coming back to TestStand.

    Reported Version:

    TestStand: 2019

    Resolved Version:

    N/A

    Added:

    Oct 11, 2021
    1141795

    Cannot Redo inserting a sequence after undoing it in full-featured UIs

    In the Full-Featured TestStand UI, when users undo inserting a sequence and then try to redo inserting a sequence, they will encounter the following error: "Index out of range. [Error Code: -17301]"

    Workaround:

    There is currently no known workaround for this issue.

    Reported Version:

    TestStand: 2019

    Resolved Version:

    N/A

    Added:

    Aug 9, 2021

    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).