Monitor Items 10

Support at least 10 MonitoredItems per Subscription where the size of each MonitoredItem is at least equal to size of Double.


Questions? Contact us
Generated: 21/11/2021 at 17:21:20 p.m.
Monitor Items 10 - 8 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

001

CTT CreateMonitoredItems()  Add the max # of monitored items (as defined by this conformance unit) to an existing subscription, using default parameters.
Step #
Action
Expected Result(s)

1

Invoke CreateMonitoredItems()

Call is successful.

2

Call Publish()

Initial data change notifications are received.

002

CTT CreateMonitoredItems()  Using default parameters (MonitoringMode=Reporting, Filter=null, QueueSize=1) to monitor multipleitems per subscription, with 3 subscriptions.
Vary the data-types of the items being subscribed to.
Vary the scan rates of the subscriptions to 100, 1000 and 5000 respectively.
ServiceResult = `Good`.
Operation level results also `Good`.

003

CTT ModifyMonitoredItems()  Modify the samplingInterval of multiple nodes, where the first half are set to 1000 msec and the latter half 3000 msec.
Where initial configuration is a subscription of 10 (or more) monitoredItems using default parameters.
Service result is `Good`.
Operation results are `Good`.

004

CTT ModifyMonitoredItems()  Invoke ModifyMonitoredItems, where:
1) Sampling period alternates 5000 & 500 msec.
2) Monitoring mode is 'Reporting' for first half of items and 'Disabled' for the remaining.
3) QueueSize increments by 2 for each item. Initial queueSize is 0.
4) DiscardOldest is True for first half of items anf False for the remaining.

Theinitial configuration is a subscription of 10 (or more) monitoredItems using default parameters.
Service result is `Good`.
Operation results are `Good`.

005

CTT Unavailable  Add 10 monitored items; 1 for the Server object's Notifier attribute, and the remaining are normal (scalar) nodes.
Step #
Action
Expected Result(s)

1

All calls are successful. The initial publish contains dataChanges and maybe events.

2

Call Publish.

All service and operation results are Good.

3

Write to a node (below the Server object) that is configured to raise an event of some kind.

All service and operation results are Good.

4

Call Publish.

Publish yields an event.

006

CTT Unavailable  EventsBase  Add 10 monitored items; multiple nodes are for the Server object's Notifier attribute; and the remaining items are normal scalar nodes.
Step #
Action
Expected Result(s)

1

All calls are successful.

2

Write to a node (below the Server object) that is configured to raise events of some kind, and also write to the monitored items.

All calls are successful.

3

Call Publish.

The initial publish contains dataChanges and Events. Each event is received multiple times; once for each monitored item that is subscribing for events.

007

CTT Unavailable  Add 11 monitored items; where the first is the Server object's Notifier attribute, and the remainder are normal (scalar) nodes.
Step #
Action
Expected Result(s)

1

The CreateMonitoredItems may reject the call if there are too many items, or reject the last item in the transaction. Otherwise, the Event(s) and DataChange notifications are in the Publish response.

2

Write to a node (below the Server object) that is configured to raise events of some kind, and also write to the monitored items.

All service and operation level results are Good.

3

Call Publish.

DataChange notifications and events received.

Err-001

CTT CreateMonitoredItems()  Specify more monitored items than the server supports within a single call to CreateMonitoredItems(). ServiceResult=`Good`.
Results[0..9]=`Good`.
Results[10..*]=`Good` or `Bad_TooManyMonitoredItems`.