Home Support Documentation Bugs

TestStand 2023 Q4 Known Issues

Created Oct 31, 2023

Overview

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

Nov 10, 2021
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:

Nov 10, 2021
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:

Jun 4, 2023
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:

Jun 4, 2023
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:

Jun 4, 2023
2187652

Extra rows get inserted when SQL INSERT statement contains 'OUTPUT INSERTED.id' clause in the "Open SQL Statement" step

Using 'OUTPUT INSERTED.id' is used in an SQL's INSERT statement in TestStand's 'Open SQL Statement' step without using the INSERTED.id subsequently, results in additional rows getting inserted into the database table.

Workaround:

Only use the SQL command OUTPUT INSERTED.id in your SQL statement if you retrieve this output and use it in your database table. For example, you can call OUTPUT INSERTED.id INTO [<table name>] (<column name>) to use the INSERTED.id value once it has been called via the OUTPUT command

Reported Version:

TestStand 2019

Resolved Version:

N/A

Added:

N/A
2190996

TestStand can produce unwanted report formatting by enabling the "Discard Results" setting when using On-The-Fly (OTF) reporting

TestStand can produce unwanted report formatting by enabling the "Discard Results" setting when using On-The-Fly (OTF) reporting. To avoid this issue, use the XML report format.

Workaround:

Use the XML reporting format.

Reported Version:

TestStand 2020

Resolved Version:

N/A

Added:

N/A
2347563

Debugging breakpoints added while debugging Python modules from TestStand using step-into operation do not properly remove themselves

Debugging breakpoints added while debugging Python modules from TestStand using step-into operation do not properly remove themselves from the module following step-into operation, and must be manually removed.

Workaround:

Manually remove the unwanted breakpoints for the code module.

Reported Version:

TestStand 2022 Q4

Resolved Version:

N/A

Added:

N/A
2529314

TestStand batch report does not append .html to UUT report links when reports are generated in separate files

When
  1. generating HTML reports using the XML or ATML batch report formats and UUTs, and
  2. the batch and UUT reports are generated in separate files,
the HTML report links on the main batch report do not include an .html extension and break.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand 2022 Q4

Resolved Version:

N/A

Added:

N/A
2548341

Does not show all exception message when DotNET code modules throw aggregate exception

TestStand does not show all exception messages when DotNET code modules throw aggregate exception. The inner exceptions are not displayed in the error message dialog.

Workaround:

Reissue the exception in the DotNET module as below:
new Exception(originalException.ToString())

Reported Version:

TestStand 2023 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
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:

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:

Nov 10, 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
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:

Jun 4, 2023

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