Address Space Events

Support OPC UA AddressSpace elements for generating Event notifications. This includes at least one Node with an EventNotifier Attribute set to True (Server Node).


Questions? Contact us
Generated: 21/11/2021 at 17:21:20 p.m.
Address Space Events - 6 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

000

CTT Walk through the address space checking the EventNotifier for each node. The Server.EventNotifier is TRUE. Record the NodeIds whose EventNotifier=true.

001

CTT Unavailable  Subscribe to receive events (Server.EventNotifier). Write to an event trigger mechanism and make sure that an event is received. An event is received.

002

CTT Unavailable  Subscribe for events for each item identified in test #0 whose EventNotifier=true. Invoke the necessary trigger methods. A max of 10 nodes. Multiple publish calls may be necessary, so keep calling until either (a) keepAlive (b) a max of #10 publish calls. The server accepts the request without error. If an event is received for a node that is NOT the server object, then the same event is also received for the Server object (same event received twice).

003

CTT CreateMonitoredItems()  Publish()  Call CreateMonitoredItems() and specify 1 item, the Server object node, and request the Notifier attribute.
Call Publish() twice.
All service and operation results are Good.
The Publish() calls may yield event notifications, or not, but no errors are to be received for the item.
Any events that are received are validated as described in the General Event Validation Checks section.

004

CTT Unavailable  CreateMonitoredItems()  Publish()  Call CreateMonitoredItems() and specify 1..n items where all-but-one has a known Notifier attribute, but exclude the Server object.
Call Publish() twice.
The CreateMonitoredItems call is Good, with each item returning Good, except for the item with no Notifier attribute which returns Bad_AttributeIdInvalid.
The Publish calls may return event notifications, or not. But, no errors will be returned for any of the items.
Any events that are received are validated as described in the General Event Validation Checks section.

005

Lab CreateMonitoredItems()  Publish()  Call CreateMonitoredItems() and specify 2 items where both have a Notifier attribute, and one of the items is the Server object, and the other item is a child of the Server object.
Cause an event to occur on the child-node.
Call Publish() twice.
All service and operation results are Good.
The first Publish() call may or may not receive an event notification, if it does then the event(s) are validated. The single event should be received twice, once per monitored item.
If the first Publish() receives the event(s) then the second Publish() will be a keep-alive; otherwise if the first Publish() was a keep-alive then the second Publish() will contain the events.