Jump to content

Unit Test Framework Error Code Family: Difference between revisions

From LabVIEW Wiki
VisualWikitext
Added page
 
m Remove redlinks for individual error code pages.
 
Line 5: Line 5:
! Description
! Description
|-
|-
| [[Error Code -25299|-25299]]
| -25299
| Unit Test Framework: Placeholder for the last Unit Test Framework error code.
| Unit Test Framework: Placeholder for the last Unit Test Framework error code.
|-
|-
| [[Error Code -25288|-25288]]
| -25288
| Unit Test Framework: Cannot access a shared variable.
| Unit Test Framework: Cannot access a shared variable.
|-
|-
| [[Error Code -25287|-25287]]
| -25287
| Unit Test Framework: An error occurred when creating test(s).
| Unit Test Framework: An error occurred when creating test(s).
|-
|-
| [[Error Code -25286|-25286]]
| -25286
| Unit Test Framework: This VI does not have a block diagram.
| Unit Test Framework: This VI does not have a block diagram.
|-
|-
| [[Error Code -25285|-25285]]
| -25285
| Unit Test Framework: Cannot execute tests while related VIs are running, including the VI under test, setup VI, teardown VI, user-defined comparison VI, and user-defined test VI.
| Unit Test Framework: Cannot execute tests while related VIs are running, including the VI under test, setup VI, teardown VI, user-defined comparison VI, and user-defined test VI.
|-
|-
| [[Error Code -25284|-25284]]
| -25284
| Unit Test Framework: This VI is in a locked library. Unlock the library or add the password in the <b>Project Properties</b> dialog box.
| Unit Test Framework: This VI is in a locked library. Unlock the library or add the password in the <b>Project Properties</b> dialog box.
|-
|-
| [[Error Code -25283|-25283]]
| -25283
| Unit Test Framework: This VI is password-protected. Unlock the VI or add the password in the <b>Project Properties</b> dialog box.
| Unit Test Framework: This VI is password-protected. Unlock the VI or add the password in the <b>Project Properties</b> dialog box.
|-
|-
| [[Error Code -25282|-25282]]
| -25282
| Unit Test Framework: The path to the user-defined test VI is invalid.
| Unit Test Framework: The path to the user-defined test VI is invalid.
|-
|-
| [[Error Code -25281|-25281]]
| -25281
| Unit Test Framework: Index not found.
| Unit Test Framework: Index not found.
|-
|-
| [[Error Code -25280|-25280]]
| -25280
| Unit Test Framework: Other error.
| Unit Test Framework: Other error.
|-
|-
| [[Error Code -25262|-25262]]
| -25262
| Unit Test Framework: The user-defined comparison VI is invalid.
| Unit Test Framework: The user-defined comparison VI is invalid.
|-
|-
| [[Error Code -25261|-25261]]
| -25261
| Unit Test Framework: The path to the user-defined comparison VI is invalid.
| Unit Test Framework: The path to the user-defined comparison VI is invalid.
|-
|-
| [[Error Code -25260|-25260]]
| -25260
| Unit Test Framework: The .lvtest file is read-only.
| Unit Test Framework: The .lvtest file is read-only.
|-
|-
| [[Error Code -25259|-25259]]
| -25259
| Unit Test Framework: The .lvtest file is invalid.
| Unit Test Framework: The .lvtest file is invalid.
|-
|-
| [[Error Code -25258|-25258]]
| -25258
| Unit Test Framework: Test Case Data Error
| Unit Test Framework: Test Case Data Error
|-
|-
| [[Error Code -25257|-25257]]
| -25257
| Unit Test Framework: Test Case Data Missing
| Unit Test Framework: Test Case Data Missing
|-
|-
| [[Error Code -25256|-25256]]
| -25256
| Unit Test Framework: An error occurred while setting input values to the VI under test.
| Unit Test Framework: An error occurred while setting input values to the VI under test.
|-
|-
| [[Error Code -25255|-25255]]
| -25255
| Unit Test Framework: No control or indicator to process.
| Unit Test Framework: No control or indicator to process.
|-
|-
| [[Error Code -25253|-25253]]
| -25253
| Unit Test Framework: If the VI under test is a reentrant VI, a dynamic dispatch member VI, a subroutine VI, or executes on a real-time (RT) target, LabVIEW can compare only the indicators on the connector pane or global variables.
| Unit Test Framework: If the VI under test is a reentrant VI, a dynamic dispatch member VI, a subroutine VI, or executes on a real-time (RT) target, LabVIEW can compare only the indicators on the connector pane or global variables.
|-
|-
| [[Error Code -25252|-25252]]
| -25252
| Unit Test Framework: If the VI under test is a reentrant VI, a dynamic dispatch member VI, a subroutine VI, or executes on a real-time (RT) target, LabVIEW can set values only to controls on the connector pane or to global variables.
| Unit Test Framework: If the VI under test is a reentrant VI, a dynamic dispatch member VI, a subroutine VI, or executes on a real-time (RT) target, LabVIEW can set values only to controls on the connector pane or to global variables.
|-
|-
| [[Error Code -25251|-25251]]
| -25251
| Unit Test Framework: LabVIEW cannot find the following control(s).
| Unit Test Framework: LabVIEW cannot find the following control(s).
|-
|-
| [[Error Code -25250|-25250]]
| -25250
| Unit Test Framework: The .lvtest file header information contains an error.
| Unit Test Framework: The .lvtest file header information contains an error.
|-
|-
| [[Error Code -25249|-25249]]
| -25249
| Unit Test Framework: The following control name is not unique.
| Unit Test Framework: The following control name is not unique.
|-
|-
| [[Error Code -25248|-25248]]
| -25248
| Unit Test Framework: The control name cannot contain the following: \n, \r, tabs, array brackets, name separators, and decimal separators.
| Unit Test Framework: The control name cannot contain the following: \n, \r, tabs, array brackets, name separators, and decimal separators.
|-
|-
| [[Error Code -25245|-25245]]
| -25245
| Unit Test Framework: An error occurred when running the setup and teardown VIs.
| Unit Test Framework: An error occurred when running the setup and teardown VIs.
|-
|-
| [[Error Code -25244|-25244]]
| -25244
| Unit Test Framework: The configuration between setup VI, teardown VI, and VI under test is invalid.
| Unit Test Framework: The configuration between setup VI, teardown VI, and VI under test is invalid.
|-
|-
| [[Error Code -25243|-25243]]
| -25243
| Unit Test Framework: Not a control reference.
| Unit Test Framework: Not a control reference.
|-
|-
| [[Error Code -25242|-25242]]
| -25242
| Unit Test Framework: The user-defined test VI is invalid.
| Unit Test Framework: The user-defined test VI is invalid.
|-
|-
| [[Error Code -25241|-25241]]
| -25241
| Unit Test Framework: The VI under test is invalid.
| Unit Test Framework: The VI under test is invalid.
|-
|-
| [[Error Code -25240|-25240]]
| -25240
| Unit Test Framework: The path to the VI under test is invalid.
| Unit Test Framework: The path to the VI under test is invalid.
|-
|-
| [[Error Code -25232|-25232]]
| -25232
| Unit Test Framework: An error occurred with the teardown VI.
| Unit Test Framework: An error occurred with the teardown VI.
|-
|-
| [[Error Code -25231|-25231]]
| -25231
| Unit Test Framework: The teardown VI is invalid.
| Unit Test Framework: The teardown VI is invalid.
|-
|-
| [[Error Code -25230|-25230]]
| -25230
| Unit Test Framework: The path to the teardown VI is invalid.
| Unit Test Framework: The path to the teardown VI is invalid.
|-
|-
| [[Error Code -25222|-25222]]
| -25222
| Unit Test Framework: LabVIEW cannot find the following terminal(s).
| Unit Test Framework: LabVIEW cannot find the following terminal(s).
|-
|-
| [[Error Code -25221|-25221]]
| -25221
| Unit Test Framework: The setup VI is invalid.
| Unit Test Framework: The setup VI is invalid.
|-
|-
| [[Error Code -25220|-25220]]
| -25220
| Unit Test Framework: The path to the setup VI is invalid.
| Unit Test Framework: The path to the setup VI is invalid.
|-
|-
| [[Error Code -25204|-25204]]
| -25204
| Unit Test Framework: Cannot load the class. Save the class before loading or executing tests.
| Unit Test Framework: Cannot load the class. Save the class before loading or executing tests.
|-
|-
| [[Error Code -25201|-25201]]
| -25201
| Unit Test Framework: Cannot open multiple instances of the <b>Unit Test Framework Results</b> window. Close the window before executing tests.
| Unit Test Framework: Cannot open multiple instances of the <b>Unit Test Framework Results</b> window. Close the window before executing tests.
|-
|-
| [[Error Code -25200|-25200]]
| -25200
| Unit Test Framework: An unknown error occurred.
| Unit Test Framework: An unknown error occurred.
|}
|}


[[Category:Error Handling]]
[[Category:Error Handling]]

Latest revision as of 15:46, 7 May 2023

Below are all of the Error Codes that belong to the Unit Test Framework Error Code Family (see Error List for list of Families).

Code Description
-25299 Unit Test Framework: Placeholder for the last Unit Test Framework error code.
-25288 Unit Test Framework: Cannot access a shared variable.
-25287 Unit Test Framework: An error occurred when creating test(s).
-25286 Unit Test Framework: This VI does not have a block diagram.
-25285 Unit Test Framework: Cannot execute tests while related VIs are running, including the VI under test, setup VI, teardown VI, user-defined comparison VI, and user-defined test VI.
-25284 Unit Test Framework: This VI is in a locked library. Unlock the library or add the password in the Project Properties dialog box.
-25283 Unit Test Framework: This VI is password-protected. Unlock the VI or add the password in the Project Properties dialog box.
-25282 Unit Test Framework: The path to the user-defined test VI is invalid.
-25281 Unit Test Framework: Index not found.
-25280 Unit Test Framework: Other error.
-25262 Unit Test Framework: The user-defined comparison VI is invalid.
-25261 Unit Test Framework: The path to the user-defined comparison VI is invalid.
-25260 Unit Test Framework: The .lvtest file is read-only.
-25259 Unit Test Framework: The .lvtest file is invalid.
-25258 Unit Test Framework: Test Case Data Error
-25257 Unit Test Framework: Test Case Data Missing
-25256 Unit Test Framework: An error occurred while setting input values to the VI under test.
-25255 Unit Test Framework: No control or indicator to process.
-25253 Unit Test Framework: If the VI under test is a reentrant VI, a dynamic dispatch member VI, a subroutine VI, or executes on a real-time (RT) target, LabVIEW can compare only the indicators on the connector pane or global variables.
-25252 Unit Test Framework: If the VI under test is a reentrant VI, a dynamic dispatch member VI, a subroutine VI, or executes on a real-time (RT) target, LabVIEW can set values only to controls on the connector pane or to global variables.
-25251 Unit Test Framework: LabVIEW cannot find the following control(s).
-25250 Unit Test Framework: The .lvtest file header information contains an error.
-25249 Unit Test Framework: The following control name is not unique.
-25248 Unit Test Framework: The control name cannot contain the following: \n, \r, tabs, array brackets, name separators, and decimal separators.
-25245 Unit Test Framework: An error occurred when running the setup and teardown VIs.
-25244 Unit Test Framework: The configuration between setup VI, teardown VI, and VI under test is invalid.
-25243 Unit Test Framework: Not a control reference.
-25242 Unit Test Framework: The user-defined test VI is invalid.
-25241 Unit Test Framework: The VI under test is invalid.
-25240 Unit Test Framework: The path to the VI under test is invalid.
-25232 Unit Test Framework: An error occurred with the teardown VI.
-25231 Unit Test Framework: The teardown VI is invalid.
-25230 Unit Test Framework: The path to the teardown VI is invalid.
-25222 Unit Test Framework: LabVIEW cannot find the following terminal(s).
-25221 Unit Test Framework: The setup VI is invalid.
-25220 Unit Test Framework: The path to the setup VI is invalid.
-25204 Unit Test Framework: Cannot load the class. Save the class before loading or executing tests.
-25201 Unit Test Framework: Cannot open multiple instances of the Unit Test Framework Results window. Close the window before executing tests.
-25200 Unit Test Framework: An unknown error occurred.
Retrieved from "https://labviewwiki.org/w/index.php?title=Unit_Test_Framework_Error_Code_Family&oldid=32021"