| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008565 | CTT UA Scripts | 1 - Script Issue | public | 2023-01-04 14:50 | 2023-02-21 15:27 |
| Reporter | Alexander Allmendinger | Assigned To | Archie Miller | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.03.501 | ||||
| Fixed in Version | 1.03.502 | ||||
| Summary | 0008565: A&C scripts printing misleading skip messages or marking tests as passed which are not run | ||||
| Description | When there is an issue in a test script of A&C the execution of the tests is aborted causing all remaining test cases to either be marked as a success or print a "No alarms discovered for ..." skip messages. But there is no indication, that the script hasn't really be executed because of the earlier issue. When the CTT is running in such an issue, there needs to be a clear indication, which scripts have been run and which did not run at all. | ||||
| Additional Information | For demonstration purposes a script in the A&C Comment CU has been broken which resulted in the attached screenshot. The screenshot shows how test cases Test_001 - Test_004 and Err_002 - Err_005 are marked as passed, though the CTT didn't even wait for events to be received (see timestamps between initialize and cleanup -> 300ms) | ||||
| Tags | No tags attached. | ||||
| Files Affected | |||||
|
|
To get more details, it is necessary to enable the Log messages, which are disabled by default. This was the only way to show pass/fails/skips image.png (73,669 bytes) |
|
|
In my case Log messages were activated as well. The output is fine, when there are no issues in the scripts. But if in one of the scripts in the CU an exception is triggered, this issue shows up. Then all following test cases are marked as passed without any log messages. |
|
|
Resolved at the same time as 8549 |
|
|
Agreed in call that other mantis issues covered this issue, closed issue |
