As described above this script requires a retransmission Queue of 6 (2 Subscriptions with 3 not Acknowledged DataChanges each). There are two Facets which are stating requirements for this queue.

Embedded DataChange Subscription Server Facet
Support of a NotificationMessage retransmission queue is not required.

Standard DataChange Subscription 2017 Server Facet
Support, as a minimum, the number of Publish requests per session as the size of the NotificationMessage retransmission queue for Republish.

This script should be moved to the "Subscription Publish Min 05" conformance unit. But still then the script needs a bigger queue then named by the profile (min. queue size 5). I would suggest to change the test case to just use a total of 4 DataChangeNotification for its test.

The script should be part of publish min 02 and publish min 05 - rework to match numbers specified in these min settings

and for min 02 allow a not supported option (if supported then it needs to be 4)

Additional comment:

The re-transmission queue is 2x the number of publishes supported - so if a server allow 3 outstanding publish requests supported then it needs to have a re-transmission queue of 6. a server is allowed to limit the number of Publish requests, if an additional request is received it shall return an error on the oldest request - limiting the umber of outstanding requests