Caraya Unit Test Framework Error Code Family: Difference between revisions
Added page |
m Remove redlinks for individual error code pages. |
||
| Line 5: | Line 5: | ||
! Description | ! Description | ||
|- | |- | ||
| | | 7000 | ||
| Caraya Test Manager: Generic Test Manager error (ex: Unhandled state) | | Caraya Test Manager: Generic Test Manager error (ex: Unhandled state) | ||
|- | |- | ||
| | | 7001 | ||
| Caraya Test Manager: Non-existent User Application Data folder | | Caraya Test Manager: Non-existent User Application Data folder | ||
|- | |- | ||
| | | 7002 | ||
| Caraya Test Manager: Test Suite failed | | Caraya Test Manager: Test Suite failed | ||
|- | |- | ||
| | | 7003 | ||
| Caraya Test Manager: Test Manager shutdown timed out | | Caraya Test Manager: Test Manager shutdown timed out | ||
|- | |- | ||
| | | 7004 | ||
| Caraya Test Manager: Cannot find assertion's caller path | | Caraya Test Manager: Cannot find assertion's caller path | ||
|- | |- | ||
| | | 7005 | ||
| Caraya Test Manager: Cannot open assertion's caller block diagram | | Caraya Test Manager: Cannot open assertion's caller block diagram | ||
|- | |- | ||
| | | 7100 | ||
| Caraya Test Runner: Cannot use the linker info in the Run time engine. | | Caraya Test Runner: Cannot use the linker info in the Run time engine. | ||
|- | |- | ||
| | | 7101 | ||
| Caraya Test Runner: At least one test is not in an executable state. | | Caraya Test Runner: At least one test is not in an executable state. | ||
|- | |- | ||
| | | 7102 | ||
| Caraya Test Runner: At least one test is not in a scope that allows it to be run programmatically. | | Caraya Test Runner: At least one test is not in a scope that allows it to be run programmatically. | ||
|- | |- | ||
| | | 7103 | ||
| Caraya Test Runner: Project reference is invalid | | Caraya Test Runner: Project reference is invalid | ||
|- | |- | ||
| | | 7104 | ||
| Caraya Test Runner: Function is not available in a real-time target | | Caraya Test Runner: Function is not available in a real-time target | ||
|- | |- | ||
| | | 7105 | ||
| Caraya Test Runner: Invalid or non-existent path | | Caraya Test Runner: Invalid or non-existent path | ||
|- | |- | ||
| | | 7106 | ||
| Caraya Test Runner: Unsupported file type | | Caraya Test Runner: Unsupported file type | ||
|- | |- | ||
| | | 7107 | ||
| Caraya Test Runner: Undefined object | | Caraya Test Runner: Undefined object | ||
|- | |- | ||
| | | 7108 | ||
| Caraya Test Runner: Library reference is invalid | | Caraya Test Runner: Library reference is invalid | ||
|- | |- | ||
| | | 7200 | ||
| Caraya Batch Tester: Generic Test Manager error (ex: Unhandled state) | | Caraya Batch Tester: Generic Test Manager error (ex: Unhandled state) | ||
|- | |- | ||
| | | 7230 | ||
| Caraya Test Report: Generic Test Report error | | Caraya Test Report: Generic Test Report error | ||
|- | |- | ||
| | | 7231 | ||
| Caraya Test Report: Invalid report path | | Caraya Test Report: Invalid report path | ||
|- | |- | ||
| | | 7232 | ||
| Caraya Test Report: Report path is empty or relative. Use an absolute path. | | Caraya Test Report: Report path is empty or relative. Use an absolute path. | ||
|- | |- | ||
| | | 7233 | ||
| Caraya Test Report: Unexpected file type | | Caraya Test Report: Unexpected file type | ||
|- | |- | ||
| | | 7234 | ||
| Caraya Test Report: Directory not found. | | Caraya Test Report: Directory not found. | ||
|} | |} | ||
[[Category:Error Handling]] | [[Category:Error Handling]] | ||
Latest revision as of 16:06, 7 May 2023
Below are all of the Error Codes that belong to the Caraya Unit Test Framework Error Code Family (see Error List for list of Families).
| Code | Description |
|---|---|
| 7000 | Caraya Test Manager: Generic Test Manager error (ex: Unhandled state) |
| 7001 | Caraya Test Manager: Non-existent User Application Data folder |
| 7002 | Caraya Test Manager: Test Suite failed |
| 7003 | Caraya Test Manager: Test Manager shutdown timed out |
| 7004 | Caraya Test Manager: Cannot find assertion's caller path |
| 7005 | Caraya Test Manager: Cannot open assertion's caller block diagram |
| 7100 | Caraya Test Runner: Cannot use the linker info in the Run time engine. |
| 7101 | Caraya Test Runner: At least one test is not in an executable state. |
| 7102 | Caraya Test Runner: At least one test is not in a scope that allows it to be run programmatically. |
| 7103 | Caraya Test Runner: Project reference is invalid |
| 7104 | Caraya Test Runner: Function is not available in a real-time target |
| 7105 | Caraya Test Runner: Invalid or non-existent path |
| 7106 | Caraya Test Runner: Unsupported file type |
| 7107 | Caraya Test Runner: Undefined object |
| 7108 | Caraya Test Runner: Library reference is invalid |
| 7200 | Caraya Batch Tester: Generic Test Manager error (ex: Unhandled state) |
| 7230 | Caraya Test Report: Generic Test Report error |
| 7231 | Caraya Test Report: Invalid report path |
| 7232 | Caraya Test Report: Report path is empty or relative. Use an absolute path. |
| 7233 | Caraya Test Report: Unexpected file type |
| 7234 | Caraya Test Report: Directory not found. |