View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002964Compliance Test Tool (CTT) Unified ArchitectureImplementation Bugpublic2015-02-12 14:372019-04-26 15:07
ReporterKenneth G. Dunahee Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionreopened 
Product Version1.02.334.200 
Summary0002964: View Services\View Basic\006.js expects bidirectional hierarchical references
Description

The test expects hierarchical references be instantiated as bidirectional.

Part 3, 5.3.2 ReferenceType NodeClass - Attributes states:
Although not required, it is recommended that all hierarchical
references be instantiated as bidirectional to ensure browse connectivity.

Steps To Reproduce

Configure address space that has a node without inverse hierarchical reference.
Configure CTT to use that node under Server Test\NodeIds\NodeClasses.
Run test.

TagsNo tags attached.
Files Affected

Relationships

related to 0004095 closedAlexander Allmendinger View Services/View Basic/006.js fails without reverse-references 

Activities

Nathan Pocock

2015-11-06 18:27

viewer   ~0006440

I'm looking at the source code and I'm not seeing this... it seems that each node is tested twice, once to get all references (forward + inverse) for all node classes, and a second time to filter by specific node class only. It then seems to check that the specific references match.

Is this still a problem in the CTT beta that you're evaluating?

Nathan Pocock

2016-01-25 17:57

viewer   ~0006575

Ken: any feedback on this issue, or can we close it?

Kenneth G. Dunahee

2016-01-26 17:08

reporter   ~0006578

The issue is still present in CTT 1.2.336.257.

View Services\View Basic\006.js line 23 references nodeClassParents[i].NodeId. When the reverse reference is populated, nodeClassParents[i].NodeId is set to the associated nodeId. When the reverse reference is not populated, nodeClassParents[i].NodeId is set to i=0. i=0 causes Error:

Test cannot be completed: the node <i=0> must have at least one reference.

To work around the issue in our testing, AddressSpace is configured to have bi-directional references.

Paul Hunkar

2018-11-09 16:28

administrator   ~0009565

This issue needs some more checking (some hierarchical reference might require an inverse reference to work)

Issue History

Date Modified Username Field Change
2015-02-12 14:37 Kenneth G. Dunahee New Issue
2015-11-06 18:27 Nathan Pocock Note Added: 0006440
2015-11-06 18:27 Nathan Pocock Assigned To => Nathan Pocock
2015-11-06 18:27 Nathan Pocock Status new => feedback
2016-01-25 17:57 Nathan Pocock Note Added: 0006575
2016-01-26 17:08 Kenneth G. Dunahee Note Added: 0006578
2016-01-26 17:08 Kenneth G. Dunahee Status feedback => assigned
2016-02-12 18:36 Nathan Pocock Status assigned => resolved
2016-02-12 18:36 Nathan Pocock Resolution open => no change required
2018-11-09 16:23 Paul Hunkar Relationship added related to 0004095
2018-11-09 16:28 Paul Hunkar Note Added: 0009565
2019-04-26 14:56 Paul Hunkar Assigned To Nathan Pocock => Alexander Allmendinger
2019-04-26 15:07 Paul Hunkar Status resolved => feedback
2019-04-26 15:07 Paul Hunkar Resolution no change required => reopened
2019-04-26 15:07 Paul Hunkar Status feedback => assigned