View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008549 | CTT UA Scripts | 1 - Script Issue | public | 2023-01-03 11:46 | 2023-02-21 15:22 |
| Reporter | Alexander Allmendinger | Assigned To | Archie Miller | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.03.501 | ||||
| Target Version | 1.03.502 | Fixed in Version | 1.03.502 | ||
| Summary | 0008549: A&C Acknowledge: Sometimes tests are skipped for types where alarms are frequently triggered | ||||
| Description | In the initialize.js the scripts calculate the MaximumTestTime with AlarmCycleTime * 3. But for example in the Acknowledge CU this is not enough time to finish all test cases so the tests are stopped with Skipped messages though it could have been tested. MaximumTestTime calculation needs to be enhanced to make sure there is sufficient time for the tests to be run. This is potentially hiding issues because test cases are not executed. | ||||
| Tags | No tags attached. | ||||
| Files Affected | |||||
| related to | 0008565 | closed | Archie Miller | A&C scripts printing misleading skip messages or marking tests as passed which are not run |
| related to | 0008566 | closed | Archie Miller | A and C Comment not using provided events for conditions |
|
|
The maximum test time should be very long - since the testing should end only when all test have been run (i.e. 15 or 20 minutes is fine) - It could be a configuration setting that could have a default or say 1 hour. Once all tets cases have been exercised then the test is complete and it ends. The time limit is just to keep it from waiting for ever for something that will not happen. |
|
|
Changing the algorithm to use ActiveState.TransitionTime to determine if a new alarm has happened will help in this regard, but it will not help for AcknowledgeableConditionType. Clarification on algorithm will be required. |
|
|
The response to the method call header timestamp would cover all cases |
|
|
Rework Acknowledge/Confirm tests to use Call ResponseHeader Timestamp as a determining factor to find new alarm conditions as opposed to acknowledged/confirmed events. Also contains improved mechanisms to determine when tests are completed, improved skips, and a minimum test run time. |
|
|
/src/main_window/qopcabstracttestcase.cpp/h /library/AlarmsAndConditions/AlarmCollector.js |
|
|
reviewed changes agreed to changes, closed issue |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-03 11:46 | Alexander Allmendinger | New Issue | |
| 2023-01-03 18:58 | Paul Hunkar | Note Added: 0018401 | |
| 2023-01-09 21:13 | Archie Miller | Note Added: 0018445 | |
| 2023-01-14 05:47 | Paul Hunkar | Note Added: 0018493 | |
| 2023-01-14 05:47 | Paul Hunkar | Assigned To | => Archie Miller |
| 2023-01-14 05:47 | Paul Hunkar | Status | new => assigned |
| 2023-01-25 21:38 | Archie Miller | Status | assigned => resolved |
| 2023-01-25 21:38 | Archie Miller | Resolution | open => fixed |
| 2023-01-25 21:38 | Archie Miller | Note Added: 0018590 | |
| 2023-01-25 21:45 | Archie Miller | Note Added: 0018591 | |
| 2023-02-03 17:17 | Archie Miller | Relationship added | related to 0008565 |
| 2023-02-18 22:43 | Paul Hunkar | Fixed in Version | => 1.03.502 |
| 2023-02-18 22:43 | Paul Hunkar | Target Version | => 1.03.502 |
| 2023-02-18 22:44 | Paul Hunkar | Status | resolved => closed |
| 2023-02-18 22:44 | Paul Hunkar | Note Added: 0018762 | |
| 2023-02-21 15:22 | Paul Hunkar | Relationship added | related to 0008566 |
