View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005663Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-05-25 05:592020-06-03 17:03
ReporterLauri Saurus Assigned ToAlexander Allmendinger  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.03.341.396 
Summary0005663: Test Data Access -> Data Access AnalogItemType-> 010.js fails with some AnalogItems defined in settings
Description

There is a problem in the test that it uses the UaNodeId.GuessType method to deduce DataType from the NodeSetting name. It does not seem to handle NodeIdWithEngineeringUnits and NodeIdWithInstrumentRange settings. It returns undefined for those nodes. Settings are located under Server Test -> NodeIds -> DA Profile -> AnalogType. Because of undefined return value the verification will fail. Should those two AnalogItems be skipped in the verification?

Steps To Reproduce

Set setting NodeIdWithEngineeringUnits and NodeIdWithInstrumentRange to valid nodes and run the test.

TagsNo tags attached.
Files Affected

Activities

Alexander Allmendinger

2020-06-02 14:57

developer   ~0012155

There are two issues in this script:

  1. Index and ClientHandles
    The script assumes that the ClientHandles are starting with 0 and uses them for the indexing of an array. But the ClientHandles start with 1 and therefore the index is always 1 off. This has been changed by introducing the analogItemIndex which works around this issue.
  2. EngineeringUnits and InstrumentRange Settings
    For those two settings of the CTT the function GuessDatatype will return and emtpy string, as it cannot get the Datatype of the configured nodes from the settings name. As a result they need to be skipped, by enhancing the if clause.

Paul Hunkar

2020-06-03 17:03

administrator   ~0012168

reviewed in CMP Call

Issue History

Date Modified Username Field Change
2020-05-25 05:59 Lauri Saurus New Issue
2020-05-27 17:28 Paul Hunkar Assigned To => Alexander Allmendinger
2020-05-27 17:28 Paul Hunkar Status new => assigned
2020-06-02 14:57 Alexander Allmendinger Status assigned => resolved
2020-06-02 14:57 Alexander Allmendinger Resolution open => fixed
2020-06-02 14:57 Alexander Allmendinger Fixed in Version => 1.03.341.396
2020-06-02 14:57 Alexander Allmendinger Note Added: 0012155
2020-06-03 17:03 Paul Hunkar Status resolved => closed
2020-06-03 17:03 Paul Hunkar Note Added: 0012168