View Client RegisterNodes

Use the RegisterNodes Service to optimize access for Nodes that are used repeatedly. Use UnregisterNodes when Nodes are not used anymore. General checks of REGISTERNODES response parameter values The following checks are performed for all valid parameter tests: Verify the nodesToRegister parameter is not null or empty. The following checks are performed for all errors with incorrect parameters tests: None defined. General checks of UNREGISTERNODES response parameter values The following checks are performed for all valid parameter tests: Validate nodesToUnregister are not null or empty. The following checks are performed for all errors with incorrect parameters tests: None defined.


Questions? Contact us
Generated: 31/20/2020 at 15:31:31 p.m.
View Client RegisterNodes - 13 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

001

RegisterNodes  Pass in a single Node Id.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

002

RegisterNodes  Pass in multiple (5 or more) valid Node Ids.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

003

RegisterNodes  Specify multiple (5 or more) valid NodeIds where some of those NodeIds originate in a remote UA Server.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

004

RegisterNodes  Pass in the same Node Id, multiple times.
Ideally the Client would avoid this and remove duplicate information.

Err-001

CTT RegisterNodes  Randomly inject one of the following status codes into the service result.
Repeat the test numerous times, each time varying the code:

1. Bad_NothingToDo.
2. Bad_TooManyOperations.
3. Bad_NodeIdInvalid.
Client handles the situation and reports the error to the end-user.

Err-002

CTT RegisterNodes  registeredNodeIds length returned is less than the nodesToRegister.
Client treats this response as if the serviceResult = Bad. Client reports a warning to the end-user that the UA Server is mis-behaving.

Err-003

RegisterNodes  registeredNodeIds length returned is greater than the nodesToRegister.
Client treats this response as if the serviceResult = Bad. Client reports a warning to the end-user that the UA Server is mis-behaving.

Err-004

Lab UnRegisterNodes  Randomly inject one of the following status codes into the service result.
Repeat the test, each time varying the code:

1. Bad_NothingToDo.
2. Bad_TooManyOperations.

005

UnRegisterNodes  Pass in a single Node Id that is currently registered (call RegisterNodes before calling UnRegisterNodes).
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

006

UnRegisterNodes  Pass in 5 valid Node Ids that are currently registered.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

007

UnRegisterNodes  Pass in the same Node Id, multiple times.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

008

UnRegisterNodes  Pass in a Node Id that has already been un-registered.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.

009

UnRegisterNodes  Pass in the Node Id that was used in the RegisterNodes call. This test is only on valid on servers that return a registered Node Id that differs from the NodeToRegister Node Id.
In all cases, this call simply returns in the outbound RegisteredNodeIds what it received in the inbound NodesToRegister, regardless of whether or not the nodes are valid or invalid.
All service results are Good.
See Part 4, section 5.8.5 paragraph 3.