View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003916Compliance Test Tool (CTT) Unified ArchitectureImplementation Bugpublic2017-08-03 09:082019-06-17 13:14
ReporterThomas Merk Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03 
Fixed in Version1.03.337 
Summary0003916: Subscription Services\Subscription Publish Min 05\Test Cases\005.js
Description

Write().Response.Results[25] is not good: BadOutOfRange (0x803c0000)

This occurs for Node Setting '/Server Test/NodeIds/Static/All Profiles/Scalar/Enumeration'.
The enumeration value is not "incremented" correctly and enumerations may return "OutOfRange" for invalid values.

Suggested changes:
Omit Enumerations from this test like:

var itemsForThisTest = [];
// use any but data type enumeration(may fail when writing incremented value)
for( var i=0; i<testItems.length; i++ ) {
    if(testItems[i].NodeSetting != "/Server Test/NodeIds/Static/All Profiles/Scalar/Enumeration") {
        itemsForThisTest.push( testItems[i] );
    }
}

and use "itemsForThisTest" everywhere instead of "testItems"

TagsNo tags attached.
Files Affected

Relationships

related to 0003967 closedAlexander Allmendinger Subscription Services\Subscription Publish Min 02\Test Cases\003.js 

Activities

Alexander Allmendinger

2017-08-04 10:15

developer   ~0008329

Solved this issue by excluding the Enumeration Node from the test cases by adding this code snipped to the initialize:
for (var i = 0; i < items.length; i++) {
if (items[i].NodeSetting != "/Server Test/NodeIds/Static/All Profiles/Scalar/Enumeration") {
testItems.push(items[i]);
}
else {
var items2 = MonitoredItem.fromSettings(Settings.ServerTest.NodeIds.Static.AllProfiles.Scalar.Settings);
if (items2 === undefined && items2 === null) continue;
testItems.push(items2[0])
addLog("Replace the Enumeration node as it currently can't be incremented. Using this node instead " + items2[0].NodeSetting);
}
}

Is fixed in the next CTT build which is supposed to be 1.03.340.348

Paul Hunkar

2019-06-17 13:14

administrator   ~0010378

reviewed in CMP call 2019-06-17

Issue History

Date Modified Username Field Change
2017-08-03 09:08 Thomas Merk New Issue
2017-08-03 14:38 Paul Hunkar Product Version => 1.03
2017-08-03 14:38 Paul Hunkar Assigned To => Paul Hunkar
2017-08-03 14:38 Paul Hunkar Status new => acknowledged
2017-08-03 16:34 Paul Hunkar Assigned To Paul Hunkar => Alexander Allmendinger
2017-08-03 16:34 Paul Hunkar Status acknowledged => assigned
2017-08-04 10:15 Alexander Allmendinger Note Added: 0008329
2017-08-04 10:15 Alexander Allmendinger Status assigned => resolved
2017-08-04 10:15 Alexander Allmendinger Fixed in Version => 1.03.337
2017-08-04 10:15 Alexander Allmendinger Resolution open => fixed
2017-11-02 14:56 Paul Hunkar Relationship added related to 0003967
2019-06-17 13:14 Paul Hunkar Status resolved => closed
2019-06-17 13:14 Paul Hunkar Note Added: 0010378