View Issue Details

IDProjectCategoryView StatusLast Update
0010324Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2025-07-03 16:24
ReporterMatti Siponen Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product Version1.04.11-01.00.508 
Summary0010324: "History > Historical Access Read Raw > 013.js" expect certain minimum lengths for array dimensions
Description

Test script "History > Historical Access Read Raw > 013.js" applies the following index ranges to 2-dimensional array Nodes: "1:3,1:3", "1:3,2:4" and "2:4,1:3".

In some cases, the 2-dimensional array Nodes used in the tests might not have sufficient dimensions for applying these index ranges and return StatusCode Bad_IndexRangeNoData. However, this StatusCode is rejected by the test script.

The "Server Test > NodeIds > HA Profile > Arrays" settings use [5,5] as an example for dimension lengths of 2-dimensional array Nodes, but it isn't specified that shorter dimension lengths would be unsupported by the tests.

Thus, the "Server Test > NodeIds > HA Profile > Arrays" settings should clearly state minimum lengths of dimensions of 2-dimensional array Nodes.

Steps To Reproduce

Use a 2-dimensional array Node where the length of each dimension is less than 4 in "Server Test > NodeIds > HA Profile > Arrays" and attempt to run the script. If the Server returns the expected StatusCode Bad_IndexRangeNoData when the index range can't be applied, the script will report it as an error.

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2025-07-03 16:21

administrator   ~0023075

on reviewing this issue and reviewing the specification - we found a number of issues - the specification says "Historians are not required to be able to store arrays. Optional ConformanceUnits exist to indicate if they support storage of arrays. If a Historian does store arrays, it may not support returning an index range in an array, it may only provide the entire array. ConformanceUnits are provided to indicate if a Historian supports index ranges." - which mean the ConformanceUnits are missing - and these test case should not be in this existing ConformanceUnit, but a different one (that currently does not exist) - will confirm this issue and then enter a related new issue for part 7 - Also if IndexRanges are not supported in general - then is it an ErrorCode (which one)? or is just the entire array returned? this is a UA working group discussion.

Next the test script should be checking if the data in the range that it is running for has the correct dimension for the test. {note if indexranges are not supported}

Issue History

Date Modified Username Field Change
2025-05-09 12:22 Matti Siponen New Issue
2025-07-03 16:21 Paul Hunkar Note Added: 0023075
2025-07-03 16:24 Paul Hunkar Assigned To => Alexander Allmendinger
2025-07-03 16:24 Paul Hunkar Status new => assigned