0005987: New test case for empty vs null ReferenceDescription[] in BrowseResult

ID	Project	Category	View Status	Date Submitted	Last Update

0005987	Compliance Test Tool (CTT) Unified Architecture	3 - Feature Request	public	2020-09-15 15:16	2022-08-18 15:21

Reporter	Kevin Herron (Inductive Automation)	Assigned To	Alexander Allmendinger
Priority	normal	Severity	minor	Reproducibility	N/A
Status	assigned	Resolution	open

Summary	0005987: New test case for empty vs null ReferenceDescription[] in BrowseResult
Description	The spec is clear that encoders and decoders shall preserve the difference between a null and empty arrays. I've observed that some servers, when returning a BrowseResult with no matches, will return a null ReferenceDescription[] array instead of an empty one. The description for BrowseResult in Part 4, Section 7.3, clearly states that this array shall be empty: The set of references that meet the criteria specified in the BrowseDescription. Empty, if no References met the criteria. The Reference Description type is defined in 7.25. I propose a test case that asserts servers return an empty array and not a null array here.
Tags	No tags attached.

Files Affected

Date Modified	Username	Field	Change
2020-09-15 15:16	Kevin Herron (Inductive Automation)	New Issue
2020-10-01 13:43	Paul Hunkar	Issue cloned: 0006110
2020-10-01 13:45	Paul Hunkar	Note Added: 0013003
2020-10-01 13:45	Paul Hunkar	Status	new => acknowledged
2020-10-01 13:46	Paul Hunkar	Relationship added	related to 0006110
2022-08-18 15:21	Paul Hunkar	Assigned To	=> Alexander Allmendinger
2022-08-18 15:21	Paul Hunkar	Status	acknowledged => assigned

Paul Hunkar 2020-10-01 13:45 administrator ~0013003	The browse part is being handled in a separate mantis issue, this is to enhance client tests and to check for other place that this type of testing should be included