/ Test prepared by Ing.-Buero Allmendinger: info@allmendinger.de
Description: Create a Durable subscription with 1 or more monitored items.
Expectation: All calls are successful. Data changes are received for each of the writes/loops in step #2. The last call to Publish is a keep-alive.
/

function subscriptionDurable008() {

The test creates a starving subscription and changes 10 times N variables.

The test makes the assumption that once the subscription is transferred, it will receive all the data changes in 10 Publish Request. the 11th been a KeepAlive Publish response.

However, some servers might decide to send the entire DataChange in response to the first PublishRequest send by the client after the subscription has been transferred, as far as the maxNotificationPerPublish limit is not violated.

The test should take into account this valid scenario.

One way of doing this would be to iterate on the PublishRequest until the KeepAlive PublishRequest is found and simply coun the total number of notification change and verify that it matches N*10.