TestStand 2025 Q3 Bug Fixes

Overview

The following items are notable issues fixed between the release of TestStand 2025 Q2 and TestStand 2025 Q3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of TestStand.

Bug Number

Legacy ID

Description

Details

2802199

Customizing the step types menu results in wrong properties set for dragged menu item

Dragging and dropping an item that is not the currently selected item in the Step Type Menu Editor dialog will result in the properties of the currently selected item to be applied on the dragged item.

Workaround:

  • Select the item you want to move before dragging it to the desired position.
    Or
  • Select the item you want to move and use the 'Move Up' and 'Move Down' buttons to move it to the desired location.

Reported Version:

TestStand: 2023 Q4

Resolved Version:

N/A

Added:

Nov 10, 2024

3058204

Opened sequence files are not reloaded if modified in the disk

User loads a file from repository in sequence editor, edits and saves the changes in the file on disk. Now if the user switches to another branch in git panel, user will not be prompted to re-load the file opened in sequence editor.

Workaround:

The reload prompt appears only after switching focus away from the Sequence Editor and returning to it.

Reported Version:

TestStand: 2025 Q2

Resolved Version:

N/A

Added:

Oct 4, 2025

3017963, 3174388

TestStand - populating TsmContext object using Expression Browser generates error

Using the Expression Browser to populate an expression with a property under SemiConductor .NET Multi Test Step causes the Sequence Editor to generate the following error:

Image

Image

This only occurs with the Semiconductor .NET Multi Test steps. The .NET action step and LabVIEW steps do not produce this error.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

STS Software Bundle: 24.5 | STS Software Bundle: 24.5.1 | STS Software Bundle: 24.5.2 | STS Software Bundle: 25.0

Resolved Version:

STS Maintenance Software: 24.5.3

Added:

N/A

3096686

Offline Git commit is not working

Offline Git commit does not function. User cannot commit changes to the local repository if you are not signed in.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2025 Q2

Resolved Version:

TestStand: 2025 Q3

Added:

N/A

3079876

Step Settings Pane crashes when hovering over a enum parameter to get tool tip

The Step Settings pane crashes when you hover over the VALUE EXPRESSION of an enum parameter.

Workaround:

"Instead of passing the enum value directly, assign the enum value to a local variable and pass that variable as the module parameter.

Reported Version:

TestStand: 2023 Q4 | TestStand: 2024 Q4 | TestStand: 2025 Q2

Resolved Version:

TestStand: 2025 Q3

Added:

N/A

3068891

TestStand incorrectly indicates that "Nothing" arguments to .NET modules are invalid

TestStand incorrectly indicates that passing the value 'Nothing' to String, Array, and other .NET code module argument types is invalid.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

STS Software Bundle: 24.5.1 | TestStand: 2023 Q4

Resolved Version:

TestStand: 2025 Q3

Added:

N/A

3066074

TestStand Array of Container indexing issue: .Name Property does not update

When copying arrays of containers containing elements with assigned names, inconsistencies in how those names are updated can occur in the following scenarios.

  • If the target array is not empty, only values/types are updated, and existing names are retained.
  • If the target array has fewer containers than the source, new containers are appended with names from the source.
  • For nested containers, names of child elements are only partially updated.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2023 Q4

Resolved Version:

TestStand: 2025 Q3

Added:

N/A

3141083

Git Pane does not load after logging into GitHub account and restarting TestStand

Logging into a Github account via the Git pane in 64-bit TestStand succeeds initially, but the Git pane fails to initialize after restarting TestStand.

Workaround:

Delete the 'Github for TestStand' credential in the Windows Credential Manager and restart TestStand.

Reported Version:

TestStand: 2025 Q2

Resolved Version:

TestStand: 2025 Q3

Added:

N/A

3143873

TestStand cannot find/load dependencies of configured assemblies in .NET step, when 'allow unload' is disabled in advanced settings

If the 'Allow unload of the assemblies specified in the step' option is disabled in the .NET ADVANCED SETTINGS for a .NET step, TestStand cannot find the dependencies for the .NET assemblies.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2024 Q4

Resolved Version:

TestStand: 2025 Q3

Added:

N/A

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

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