Discovery Client Find Servers on Network using LDS-ME

Use FindServersOnNetwork Service to obtain URLs for specific Server URIs. Note that this Service is available via the Local Discovery Server with multicast extension (LDS-ME).


Questions? Contact us
Generated: 22/11/2021 at 17:22:12 p.m.
Discovery Client Find Servers on Network using LDS-ME - 13 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

001

Lab FindServersOnNetwork  Client calls FindServersOnNetwork using valid parameters.
Step #
Action
Expected Result(s)

1

All parameters are specified correctly, based on user-input (if applicable).

2

Select a Server from the returned list, and connect to it.

The connection is successful (assuming security is setup)

3

Repeat the above step for Servers hosted on other computers on the network.

The connection is successful (assuming security is setup)

002

FindServersOnNetwork  Client specifies one or more 'serverCapabilityFilters' All parameters are specified correctly, based on user-input (if applicable).

003

Lab FindServersOnNetwork  Invoke FindServersOnNetwork to get a baseline of available servers.
Step #
Action
Expected Result(s)

1

Client processes results appropriately.

2

Unregister a server so that it is removed from the LDS. Invoke FindServersOnNetwork. Hint: Hint: we expect the LDS to specify an update value in 'lastCounterResetTime'

Client refreshes its list to show the new list of available servers.

004

Lab FindServersOnNetwork  With multiple computers available, each with an LDS and Servers; call FindServersOnNetwork.
Step #
Action
Expected Result(s)

1

Client displays/processes the list of returned servers.

2

Remove one or more computers from the network, and call FindServersOnNetwork again.

Client adjusts the list of returned servers it displays/uses. Other servers are either removed or flagged as unavailable.

005

CTT Unavailable  FindServersOnNetwork  Reset the lastCounterResetTime to 0. Client may ignore this error and continue processing the response.

006

CTT Unavailable  FindServersOnNetwork  Reset the lastCounterResetTime to a value in the future, i.e. "tomorrow". Client may ignore this error and continue processing the response.

007

CTT Unavailable  FindServersOnNetwork  Clear the 'servers' parameter. Client handles the situation by displaying an empty screen, logging a message that no records were returned, or whatever is appropriate for the client.

008

CTT Unavailable  FindServersOnNetwork  Return more records than specified by the 'maxRecordsToReturn' parameter. Skip test if client does not specify a maxRecordsToReturn. Client utilizes the information received. Client may ignore the extra records, or display/use them.

009

CTT Unavailable  FindServersOnNetwork  Modify the 'recordId' parameter so all of the records have the same id. Client detects the duplicated ids, rejects them, and reports an error.

010

CTT Unavailable  FindServersOnNetwork  Modify the first record in the collection so that the 'serverName' is empty. Client rejects the record and indicates the problem, perhaps hides the server, showing a different color, etc.

011

CTT Unavailable  FindServersOnNetwork  Modify the first record in the collection so that the 'discoveryUrl' is empty.
Step #
Action
Expected Result(s)

1

Client rejects the record and indicates the problem, perhaps hides the server, showing a different color, etc.

2

Modify the first record in the collection so that the 'discoveryUrl' is invalid, i.e. "the quick brown fox…"

Client rejects the record and indicates the problem, perhaps hides the server, showing a different color, etc.

3

Modify the first record in the collection so that the 'discoveryUrl' is invalid, i.e. "opc.tcp://192.168.0.0.1:4840"

Hopefully the client can detect this kind of error; if not, then it is able to handle the failure when trying to connect.

012

CTT Unavailable  FindServersOnNetwork  Modify the first record in the collection so that the 'serverCapabilities' is empty. Client accepts the record and simply does not show any capabilities.

013

CTT Unavailable  FindServersOnNetwork  Return records that do not match the client's filter, i.e. Request "DA" but only receive "HA" (no "DA"). Vary the filter criteria. Client rejects the record and indicates the problem, perhaps hides the server, showing a different color, etc.