View Issue Details

IDProjectCategoryView StatusLast Update
0007039Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2021-07-09 15:13
ReporterJochen Baier Assigned ToSebastian Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.04.09.398 
Fixed in Version1.03.341.399 
Summary0007039: Script: Monitored Item Services->Monitor Triggering->Err-011.js: items cloned wrong: Test fails
Description

The script Monitored Item Services->Monitor Triggering->Err-011.js clone the tempItems from items wrong:

var tempItems = [];
for (var i = 0; i < items.length; i++) tempItems = items[i].clone();

after this tempItems is no array anymore and contains only the the last element from items.

Proposed fix:

for (var i = 0; i < items.length; i++)
{
tempItems[i] = items[i].clone();
}

Without this fix the test fails on my setup with: 'SetTriggering().Response.AddResults[0] = Good but MonitoredItemIdInvalid was expected'

TagsNo tags attached.
Files Affected

Activities

Sebastian Allmendinger

2021-07-05 12:24

developer   ~0014636

In the mentioned code there is indeed an issue. But after reviewing the test script, a different approach has been prepared.
The intension of "tempItems" was to reduce the possibilty that the MonitoredItemId of the linked item is identical to the MonitoredItemId of the triggering item, because this results in exactly the described behavior (SetTriggering succeeds).
An updated test script has been prepared, that creates 2 Subscriptions. In the first one (which is the "default" subscription used in the entire conformance unit) only 1 MonitoredItem, that will be used as triggering item, will be created. In the second subscription, 2 MonitoredItems will be created. Because MonitoredItemsIds shall be unique within a subscription, at least one of these items must have a different Id than the triggering item. The updated test script will check this and will try to add a link to the MonitoredItem with the different id.

Paul Hunkar

2021-07-09 15:13

administrator   ~0014676

review in cmp call, agreed to changes and closed

Issue History

Date Modified Username Field Change
2021-06-22 08:20 Jochen Baier New Issue
2021-07-02 16:01 Paul Hunkar Assigned To => Alexander Allmendinger
2021-07-02 16:01 Paul Hunkar Status new => assigned
2021-07-05 12:24 Sebastian Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2021-07-05 12:24 Sebastian Allmendinger Status assigned => resolved
2021-07-05 12:24 Sebastian Allmendinger Resolution open => fixed
2021-07-05 12:24 Sebastian Allmendinger Fixed in Version => 1.03.341.399
2021-07-05 12:24 Sebastian Allmendinger Note Added: 0014636
2021-07-09 15:13 Paul Hunkar Status resolved => closed
2021-07-09 15:13 Paul Hunkar Note Added: 0014676