The following items are notable issues fixed between the release of TestStand 2024 Q4 and TestStand 2025 Q2, 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 |
|---|---|---|---|
| 2938931, 3004962 |
Error -17502 encountered when using a custom step type that calls a .NET assembly as a Post-Step/Edit Substep with LabVIEW adapterWhen a custom step type calls into a .NET assembly using the Edit or Post-Step Substep and the Adapter is set as 'LabVIEW', error -17502 is encountered when accessing the .NET code for the Edit or Post-Step Substeps.
Workaround: Set the custom step type adapter to 'None'. Note: In TestStand 2024 Q4 and newer, the .NET adapter executes code using .NET 8.0, so the execution of .NET Framework code modules in .NET 8.0+ may encounter incompatibilities. Please refer to https://www.ni.com/docs/en-US/bundle/teststand/page/teststand-new-features-and-changes.html#d37548e60 for incompatibilities to avoid in your .NET code to ensure it executes in .NET 8.0
|
Reported Version: TestStand: 2024 Q4 Resolved Version: TestStand: 2025 Q2 Added: Jan 31, 2025 |
|
| 2932135, 3004962 |
Report generated by File Diff and Merge utility renders empty in a browserThe sequence file comparison report generated by the TestStand File Diff and Merge utility appears empty when viewed in a browser.
Workaround: Open the file 'C:\Program Files (x86)\National Instruments\TestStand 2024\Components\Stylesheets\FileDiffer\DifferStylesheet.xslt' and update the value 'xmlns:fd="http://www.ni.com/TestStand/23.0.0/DifferReport" ' to 'xmlns:fd="http://www.ni.com/TestStand/24.0.0/DifferReport" '. Note: For 64-bit, the file is located at 'C:\Program Files\National Instruments\TestStand 2024\Components\Stylesheets\FileDiffer\DifferStylesheet.xslt' |
Reported Version: TestStand: 2024 Q4 Resolved Version: TestStand: 2025 Q2 Added: Jan 31, 2025 |
|
| 2958845, 3004962 |
DAQmx .NET Framework Assembly does not load in TestStand .NET adapterCalling into the DAQmx .NET API using the TestStand .NET adapter step type throws an exception stating that the mixed assembly could not be loaded into a collectible AssemblyLoadContext. The TestStand .NET adapter tries to load the DAQmx .NET API assembly using the .NET 8 AssemblyLoadContext. This causes a failure as the .NET 8 AssemblyLoadContext does not support loading mixed-mode assemblies, and the DAQmx .NET API assembly is mixed-mode. The AssemblyLoadContext is collectible to allow unloading of assemblies that are loaded in the .NET adapter.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2024 Q4 Resolved Version: TestStand: 2025 Q2 Added: Jan 31, 2025 |
|
| 2901007 |
Deadlock Issue with LabVIEW VI Using Namespace in Batch ModelWhen a user runs a TestStand sequence using the Batch execution model and includes a LabVIEW step that calls a VI from within a namespace (such as a PPL-Packed Library or library), a deadlock issue may occur if the VI has an enum parameter. At the start of execution, TestStand preloads steps as expected. However, when an enum is involved, TestStand attempts to reload the VI to retrieve the enum to TestStand number mapping required for execution. This secondary loading introduces a locking conflict in the above scenario. As a result, TestStand execution may hang, the execution never completes, and CPU usage spikes significantly.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2021 SP1 Resolved Version: TestStand: 2025 Q2 Added: Apr 11, 2025 |
|
| 2903480 |
Unable to import specifications from SCM serverThe Specification Compliance Manager (SCM) tool in TestStand is used to import product specifications from an external SCM server into a sequence file. These specifications are added as variables allowing users to configure test limits, sweeps, and measurement conditions based on the imported data. In TestStand 2024Q4, user fails to load specifications into the sequence file. Although the user can connect to the SCM server and select a product, the data is not stored as expected. The issue arises from the fact that the selected sequence file and sequence are not passed properly to the tool. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2024 Q4 Resolved Version: TestStand: 2025 Q2 Added: Apr 11, 2025 |
|
| 2935036 |
TestStand Sequence Editor UI unexpected behavior.When the user clicks the Restore Down button to switch from maximized to windowed mode, the right-hand panes—specifically the Variables and Sequences panels—unexpectedly disappear. These panes are expected to remain docked to the right side and resize accordingly, just as they did in previous versions. Instead, only the Steps view remains visible. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2024 Q4 Resolved Version: TestStand: 2025 Q2 Added: Apr 11, 2025 |
|
| 2966210 |
TestStand - Steps Pane is not seen by default during Sequence ExecutionIn the Sequence Editor, after executing a sequence, if a specific tab (e.g., Report View) is explicitly selected and the execution is restarted, the view does not correctly switch back to the Steps View. Instead, it remains on the previously selected tab throughout the execution. This behavior is observed only in the "Test UUTs" execution mode. In contrast, in the "Single Pass" execution mode, the pane switches to the Steps pane upon restarting execution. Additionally, clicking anywhere outside the selected pane removes its focus, causing the Steps pane to become visible. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2022 Q4 | TestStand: 2023 Q4 | TestStand: 2024 Q4 Resolved Version: TestStand: 2025 Q2 Added: Apr 11, 2025 |
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.