View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008567 | CTT UA Test Case | 4 - Test Case Definition | public | 2023-01-04 15:06 | 2025-03-07 19:05 |
Reporter | Alexander Allmendinger | Assigned To | Archie Miller | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | 1.03.09.501 | ||||
Summary | 0008567: A & C Tests are run on the next received event no matter of the state machine | ||||
Description | A&C Tests are run on the next received event (inactive or active, retained or not retained ...). In some of the products used to validate the test scripts the behavior for active and not active conditions is different. E.g. if the server does not maintain knowledge of previously available events and removes the events from its memory when they become inactive (not storing alarms/events internally) then calls using the EventId (e.g. AddComment) will result in a Bad_UnkownNodeId or similar. The specification is silent on the difference between active and inactive events, so test cases and scripts need to be changed to allow both options or spec needs to be clarified. This mantis needs to be clone to fix the test script or spec based on discussion outcome. | ||||
Tags | No tags attached. | ||||
Files Affected | |||||
related to | 0010190 | new | Compliance Test Tool (CTT) Unified Architecture | A & C CertificateExpiration tests do not respect timestamp differences | |
related to | 0010191 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Shelving tests do not respect timestamp differences | |
related to | 0010195 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Suppression tests do not respect timestamp differences | |
related to | 0010206 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Limit tests do not respect timestamp differences | |
related to | 0010207 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Discrete tests do not respect timestamp differences | |
related to | 0010208 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Comment tests do not respect timestamp differences | |
related to | 0010209 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Confirm tests do not respect timestamp differences | |
related to | 0010210 | new | Compliance Test Tool (CTT) Unified Architecture | A and C Acknowledge tests do not respect timestamp differences |
|
The alarm model should be processed based on the statemachine exposed as part of the event. Each test needs to be run only on event that are in the correct state for the test. We need to first generate the required starting state for each test case/condition [note: some can apply to many states like comment - which can apply to many states] |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-01-04 15:06 | Alexander Allmendinger | New Issue | |
2023-02-03 15:59 | Paul Hunkar | Note Added: 0018662 | |
2023-02-03 15:59 | Paul Hunkar | Assigned To | => Archie Miller |
2023-02-03 15:59 | Paul Hunkar | Status | new => assigned |
2025-03-05 23:07 | Archie Miller | Relationship added | related to 0010190 |
2025-03-05 23:08 | Archie Miller | Relationship added | related to 0010191 |
2025-03-05 23:23 | Archie Miller | Relationship added | related to 0010195 |
2025-03-07 18:03 | Archie Miller | Relationship added | related to 0010206 |
2025-03-07 18:09 | Archie Miller | Relationship added | related to 0010207 |
2025-03-07 19:04 | Archie Miller | Relationship added | related to 0010208 |
2025-03-07 19:05 | Archie Miller | Relationship added | related to 0010209 |
2025-03-07 19:05 | Archie Miller | Relationship added | related to 0010210 |