A & C Instances

Support the exposing of A&C Conditions in the AddressSpace.


Questions? Contact us
Generated: 21/11/2021 at 17:21:20 p.m.
A & C Instances - 4 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

000

CTT Unavailable  Walk through the address space looking for Condition instances. For each instance, check its data-type compliance. The CTT may contain settings to facilitate direct access to Condition instances. Each condition instance contains a reference to the ConditionType. All nested properties and methods comply to the Type definition.

Spec Link: P9->Table 7

001

CTT Unavailable  For each configured condition instance, invoke the DISABLE method and then read the Retain property value. Alarm in a non-alarmed state!
Step #
Action
Expected Result(s)

1

Each call is successful. The Retain property is FALSE. Service / operation result: GOOD. Spec Link: P9->5.5.2 page 18 1st bullet

2

Write to the triggering node (to invoke an event) and call Publish.

The disabled event is NOT received. Service / Operation Result = GOOD. Spec Link: P9->5.5.2 page 18 3rd bullet

3

Then, for each condition instance invoke the ENABLE method and then read the Retain property value. Note: The previous step set the condition into an alarm state!

Each call is successful. The Retain property is TRUE. Service / Operation Result = GOOD. Spec Link: P9->5.5.2 page 18 2nd bullet

4

Call Publish.

The event is received.

002

CTT Unavailable  For each configured condition instance, invoke the ADDCOMMENT method and specify a comment for a given event. AddComment is OPTIONAL behavior so this test must be allowed to exit gracefully (skip) if not supported. An event notification must be received in advance to have the eventId.
Step #
Action
Expected Result(s)

1

Call is successful. Service / operation results: Good.

2

Trigger the event associated with the condition and then call Publish.

Event notification received containing the comment from the previous step.

003

CTT Unavailable  For each configured condition instance, invoke the CONDITIONREFRESH method.
Note: Follow the instance reference to find it's type Definition for invoking the method.
No conditions should be active prior.
Step #
Action
Expected Result(s)

1

Calls successful. No conditions should be returned. Service / operation results: GOOD.

2

Repeat the previous step. Note: Write to a trigger node to make at least one condition active!

Calls successful. Any conditions received match the CTT's expectations. Service / operation results: GOOD.