Base Info EventQueueOverflowEventType

The Server supports the EventQueueOverflowEventType as defined in Part 4


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

001

Lab CreateMonitoredItems()  Call CreateMonitoredItems() while specifying the Notifier attribute for a node that supports events, the RequestedQueueSize=1.
Invoke an action that will generate an event for the monitored item.
Call Publish().
Repeat the action to generate the event, twice.
Call Publish().

TIP: Use the script ”001.js” in the CTT’s conformance unit.
CreateMonitoredItems() is Good, results Good too.
Publish() #1 is Good, any events received may be ignored; otherwise noone events are is expected.
Publish() #2 is also Good, any events received are validated. The EventQueueOverflow event type is expected for the monitored item.

NOTE: Use the CTT script which has “wait(30000)” before each Publish call so as to provide the human with enough time to generate the event.

002

Lab CreateMonitoredItems()  Publish()  Call CreateMonitoredItems() while specifying the Notifier attribute for a DIFFERENT node (from test 001) that supports events, the RequestedQueueSize=1.
Invoke an action that will generate an event for the monitored item.
Call Publish().
Repeat the action to generate the event, twice.
Call Publish().

TIP: Use the script ”001.js” in the CTT’s conformance unit.
CreateMonitoredItems() is Good, results Good too.
Publish() #1 is Good, any events received may be ignored; otherwise noone events are is expected.
Publish() #2 is also Good, any events received are validated. The EventQueueOverflow event type is expected for the monitored item.

NOTE: Use the CTT script which has “wait(30000)” before each Publish call so as to provide the human with enough time to generate the event.

003

CTT Unavailable  Call CreateMonitoredItems() while specifying the Notifier.SubscribeToEvents attribute for a node that supports events, the RequestedQueueSize=2. Invoke an action that will generate an event for the monitored item. Repeat this enough times to exceed the RevisedQueueSize in CreateMonitoreItems. Call Publish(). CreateMonitoredItems() is Good, results Good too. Publish yields 2 events plus the EventQueueOverflow event type is expected for the monitored item (requested QueueSize=2, but the reality is that the overflow event is actually a 3rd queued item). Validate the EventQueueOverflowEventType event (source node matches expectations).

004

CTT Unavailable  Repeat #3 but with different queue sizes, e.g. 5, 10, 50. as test #1