TestStand 2021 Known Issues

Overview

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

903304

LabVIEW full-featured user interface crashes when using 'CommandKind_ToggleBreakpoint' in ExecutionViewManager

If the cmdKind Enum in IExecutionViewMgr is set to CommandKind_ToggleBreakpoint in UserInterfaces\Full-Featured\LabVIEW\Source Code\TestExec.llb\Configure ExecutionView Manager.vi, the full-featured LabVIEW user interface crashes when a breakpoint is applied in any test sequence.

This issue was observed specifically when the above changes were made to associate the Terminate/Restart button with the ToggleBreakpoint command, the UserInterfaces\Full-Featured\LabVIEW\Source Code\TestExec.llb\Top-Level VI.vi was executed, a sequence file was loaded, and a breakpoint was applied to a step.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2017 SP1

Resolved Version:

N/A

Added:

N/A

1127168

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:

Sep 8, 2021

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:

N/A

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:

Sep 8, 2021

1144328

Doing 'SaveAs Previous' resets the values of Python and LV NXG adapter specific extended data types to default in the original file

When you create a sequence file in TestStand 2020 that has custom data types with non-default values, saving it in a previous version resets the values to default. This is an issue with the Python and LabVIEW NXG adapters.


Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

Sep 8, 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:

N/A

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:

N/A

1210473

Changes to sub-elements of a cluster within an array of cluster do not get updated

When changes occur within an array of clusters which is a sub-element of a VI parameter, TestStand does not detect the changes when updating a TS custom data type to match the VI parameter.

This happens for an array of clusters that is within a cluster or an array of clusters. TestStand detects changes in elements to the first level of clusters but not to any changes in the next level of the clusters.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2019

Resolved Version:

N/A

Added:

N/A

1358314

Values of sequence call parameters are lost after deleting parameters from called sequence

Parameter values are lost from a Sequence Call step when a parameter in the step uses the default value, then you remove the parameter from the called subsequence and reload the Sequence Call step.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2017

Resolved Version:

N/A

Added:

N/A

1440035

TestStand hangs when Sweep Loop step generates a large number of values for a parameter

When a parameter in a Sweep Loop step is configured in a way that generates a large set of values, TestStand hangs while executing the step until the generation of the values is complete.

Workaround:

There is currently no known workaround for this issue.
TestStand 2021 limits the number of values for a parameter to 300,000.

Reported Version:

TestStand: 2021

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:

N/A

1558674

Error 'Error occurred during processing request' displayed when filter is applied to a parameter and the Test Vector Table is refreshed

If the Test Vector Table is open with a filter applied to a parameter, and you modify the step settings of the Sweep Loop step so they are out of sync with the Test Vector Table, TestStand displays "Error occurred during processing request" when you refresh the Test Vector Table.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2021

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

959623

Some LabVIEW Classes cannot be found in vi.lib, user.lib, or instr.lib

When you create Action steps that call LabVIEW class members from classes located in vi.lib, user.lib, or instr.lib, TestStand returns edit time errors. The VI icons and parameters are not loaded when these errors occur. The errors may occur whether you select to use an absolute or relative path to the LabVIEW class.

After placing the step, the following error may occur:

LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.


When going back to step after clicking off of it, the following error may occur:
 
The parameters specified by the step do not match the controls and indicators of the VI, or the VI may be broken.

Click this icon to reload the prototype, which maps the current arguments to the controls and indicators wired to the VI connector pane.

If the error persists, open the VI in the LabVIEW development System and ensure it is not broken.

Workaround:

Open the class in LabVIEW and then TestStand will load them correctly.

Reported Version:

TestStand: 2017 SP1

Resolved Version:

N/A

Added:

Sep 8, 2021

220932 676017

The Edit Code button for a C++ DLL does not work with Visual Studio 2017

The Edit Code button will not work when targeting a C++ DLL project built with Visual Studio 2017.

Workaround:

Manually open the Visual Studio 2017 project.

Reported Version:

TestStand: 2016

Resolved Version:

N/A

Added:

Jan 26, 2018

220844, 959623 390139

VIs in a LabVIEW project saved in the instr.lib directory fail to load when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine

Calling a VI code module returns a <strong><code>File Not Found</code></strong> error when all of the following conditions are true:<ul><li>A LabVIEW project contains the VI and a TestStand step specifies the project</li><li>The LabVIEW project file is saved in the <code>instr.lib</code> or <code>vi.lib</code> directory</li><li>You configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine</li></ul>This error occurs because TestStand incorrectly generates the VI file path by replacing <code>LabVIEW\</code> with <code>TestStand\bin\</code>. This issue does not occur on a deployment target computer because the TestStand Deployment Utility moves the dependencies to a different location that does not experience this issue.

Workaround:

Call the VI directly and do not specify a project path.

Reported Version:

TestStand: 2010 SP1

Resolved Version:

N/A

Added:

Jun 28, 2013

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