The following items are notable issues fixed between the release of TestStand 2022 Q4 and TestStand 2023 Q4, 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 |
|---|---|---|---|
| 1370979 |
TestStand Report displays different variant of graph the first timeWhen 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: TestStand 2023 Q4 Added: May 31, 2022 |
|
| 1913434 |
Wrong version number of LabVIEW project library created with the TestStand Deployment UtilityIn 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: TestStand 2023 Q4 Added: May 31, 2022 |
|
| 2142192 |
The Jedi package makes the Python step slow to display module details when a large number of Python modules are installedWhen the Jedi package is installed, Python steps can respond slowly at edit time when users interact with the different step setting controls that collect data from the configured Python module. This slowness occurs when there are a large number of Python packages installed, resulting in a large number of Python modules for Jedi to access or parse.
Workaround: Uninstall the Jedi package so TestStand does not use the new parser.
|
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: Jun 4, 2023 |
|
| 2187010 |
The LabVIEW adapter truncates the namespace of VI when its full path is longer than MAXPATHThe LabVIEW adapter incorrectly truncates the namespace of the VI when the length of the VI's path plus the namespace is longer than MAXPATH.
Workaround: Place VIs in shorter directory paths.
|
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: Jun 4, 2023 |
|
| 2221191 |
Images in column headers are not displayedImages in the column headers are not displayed. This affects those column headers that have an image, e.g., Level and Write to Output Stream in the Sweep Loop step, or Include in Report, Is Measurement, and Is Limit in Additional Results.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: Jun 4, 2023 |
|
| 2153878 |
In HTML report and On-The-Fly reports with filtering expression, separator lines are added in the report for steps that are not loggedIn HTML and On-The-Fly (OTF) reports, separator lines are added to the resulting report for each step result, even if that step result wasn't logged because of a filtering expression. Note: This issue is not observed for other report
formats, like ATML 5.00.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2020 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2246032 |
Opening the Properties pane for the WorkSpaceObject datatype causes TestStand to crashWhen trying to open the properties for 'WorkSpaceObject' under the Standard Data Types, Sequence Editor crashes.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2259695 |
TestStand does not support Python NumPy library version 1.24NumPy 1.24 has made changes which breaks TestStand-Python integration that uses NumPy.
Workaround: Use an earlier version of NumPy if NumPy 1.24 is not essential |
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2262019 |
TestStand crashes when a message popup step which displays an image is called in the SequenceFileLoad callbackTestStand crashes when a message popup step which displays an image is called in the SequenceFileLoad callback. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2021 SP1 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2266577 |
Logging a numeric reference output parameter when no value expression is specified results in an errorWhen logging values of a LV reference parameter when the reference is of type number (as opposed to LV class, ActiveX or .Net) and the output parameter is not assigned an output variable but is still logged, results in error.
Workaround: Ensure you assign the the output parameter of each LV reference parameter to an output variable. |
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2281171 |
Step references are not formatted by name for the Do-While step's descriptionThe description for the Do-While step does not show the step name with the unique ID as is shown for the If- step. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2302944 |
TestStand fails to parse a Python script if it contains Unicode quotation charactersWhen a Python code module, called from TestStand, contains Unicode quotation character, like U+201C, TestStand is not able to parse the Python module at edit time to get the list of attributes, classes and functions. Workaround: Use the ASCII quotation character in the Python code module.
|
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2380687 |
Using relative path for Python virtual environment, TestStand analyzer fails to validate the pathUser can configure at step level, what Python interpreter to use. When user configures relative path for Python virtual environment, TestStand analyzer fails to validate the path.
Workaround: Use absolute path for the configured Python virtual environment.
|
Reported Version: TestStand 2020 Resolved Version: TestStand 2023 Q4 Added: N/A |
|
| 2292246 |
Shutting down the LabVIEW Simple UI when the LabVIEW RTE used to run modules is also used to execute the UI itself results in delayWhen the LabVIEW simple UI is executed using the LabVIEW RTE that the same RTE is also used to execute LabVIEW code modules results is delay when shutting down the LabVIEW Simple UI.
Workaround: Set the following Key in the Adpaters.cfg file to false: <_FlexGAdp_WaitForLVRTECleanupAtShutdown classname='Bool'> <value>false</value> </_FlexGAdp_WaitForLVRTECleanupAtShutdown> |
Reported Version: TestStand 2022 Q4 Resolved Version: TestStand 2023 Q4 Added: N/A |
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.