Attribute Client Read Complex

Read and decode ComplexData (structures).


Questions? Contact us
Generated: 22/11/2021 at 17:22:12 p.m.
Attribute Client Read Complex - 9 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

001

Lab Read  Read a variable of type 'structure', where the type is a native OPC UA type such as ServerState. Client is able to read, process, and use (e.g. display, log, alert, etc.) the structured value.

002

Lab Read  Read a variable of type 'structure', where the type is vendor-defined or user-defined, and the structure is relatively simple, i.e. 1-level deep. Insert a CTT in the middle to observe the behavior Client is able to read, process, and display (if applicable) the structured value.
Note: The client is expected to traverse the type definition database to retrieve the definition from the type-dictionary in order to process the structure; so multiple browse/read calls should be observed either on startup or as part of the read.

003

Lab Read  Read a variable of type 'structure', where the type is vendor-defined or user-defined, and the structure is multiple levels deep. If Client supports multi-level structures Client is able to read, process, and display (if applicable) the structured value.
Note: The client is expected to traverse the type definition database to retrieve the definition from the type-dictionary in order to process the structure; so multiple browse/read calls should be observed either on startup or as part of the read.

004

CTT Unavailable  Read a variable of type 'structure', but one or more fields are missing (structure does not comply with the definition) CTT: script should remove some bytes from the ByteString. Client detects the fault, handles it, logs an error, and ultimately ignores the value by overriding the StatusCode to Bad.

005

CTT Unavailable  inject wrong type definition into Read.Response…ExtensionObject.TypeId. CTT: script should require the tester to specify the NodeId of the structure that is to be modified. Client is unable to validate the structure. A Bad_DecodingError is logged somewhere.

006

Lab Read a structure and verify the client is able to decode using all supported encodings, i.e. "Default Binary" and "Default XML" etc. Client is able to read, process, and display (if applicable) the structured value.
Note: The client is expected to traverse the type definition database to retrieve the definition from the type-dictionary in order to process the structure; so multiple browse/read calls should be observed either on startup or as part of the read.

007

CTT Unavailable  Read a Structure that uses inheritence… issue a Read for the "parent" Type and inject the "child" type into the ExtensionObject.TypeId. Note: The UA Reference Server needs to be extended to have two structures defined where the ""child"" extends the ""master"" by adding one more field. CTT script can be developed to switch the ExtensionObject.TypeId to the ""other"" NodeId, e.g. Parent>Child and Child>Parent, etc. Client is unable to validate the structure. A Bad_DecodingError is logged somewhere.

008

CTT Unavailable  Read a Structure that uses inheritence… issue a Read for the "child" type and inject the "parent" type into the ExtensionObject.TypeId. Note: The UA Reference Server needs to be extended to have two structures defined where the ""child"" extends the ""master"" by adding one more field. CTT script can be developed to switch the ExtensionObject.TypeId to the ""other"" NodeId, e.g. Parent>Child and Child>Parent, etc. Client is unable to validate the structure. A Bad_DecodingError is logged somewhere.

009

CTT Unavailable  Inject a structure with an alternate encoding, i.e. client expects Binary but actually receives XML; and vice-versa. Client is unable to validate the structure. A Bad_DecodingError is logged somewhere.