View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006110Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2020-10-01 13:432020-10-02 14:12
ReporterPaul Hunkar Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Fixed in Version1.03.341.397 
Summary0006110: 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.

Additional Information

This clone is to test the browse functionality - the main issue will require other enhancement (thus breaking it into two issues)

this should be added to viewbasic - good test case

TagsNo tags attached.
Files Affected

Relationships

related to 0005987 assignedAlexander Allmendinger New test case for empty vs null ReferenceDescription[] in BrowseResult 

Activities

Alexander Allmendinger

2020-10-02 14:01

developer   ~0013004

Added a new test case to the Conformance Unit View Basic

Test Case:
Validate that the server returns an empty BrowseDescriptions when no reference is matching the filter criteria. SpecLink: 7.6. BrowseResult
Test Step:
Create an BrowseRequest with a filter which results in an empty list of references to be provided in the BrowseResult
Expected Result:
ReferenceDescriptions is empty and NOT null.

Paul Hunkar

2020-10-02 14:11

administrator   ~0013005

reviewed in cmp call

Issue History

Date Modified Username Field Change
2020-10-01 13:43 Paul Hunkar New Issue
2020-10-01 13:43 Paul Hunkar Issue generated from: 0005987
2020-10-01 13:43 Paul Hunkar Assigned To => Alexander Allmendinger
2020-10-01 13:43 Paul Hunkar Status new => assigned
2020-10-01 13:46 Paul Hunkar Relationship added related to 0005987
2020-10-02 14:01 Alexander Allmendinger Status assigned => resolved
2020-10-02 14:01 Alexander Allmendinger Resolution open => fixed
2020-10-02 14:01 Alexander Allmendinger Fixed in Version => 1.03.341.397
2020-10-02 14:01 Alexander Allmendinger Note Added: 0013004
2020-10-02 14:11 Paul Hunkar Status resolved => closed
2020-10-02 14:11 Paul Hunkar Note Added: 0013005
2020-10-02 14:12 Paul Hunkar Issue cloned: 0006115