View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004635Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2019-02-22 08:182019-07-18 13:07
ReporterBernd Edlinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03.341.384Fixed in Version1.03.341.390 
Summary0004635: Address Space Model/Address Space Base/001.js fails
Description

CTT: 1.03.341.385

We have a test variable that has a BAD status code, it is there to be able to test that we are able to return a status code in the Read Request.
It is there since ever.

However the latest CTT version browses the name space of Micro/Nano servers and finds this variable.

That triggers an error:

Read.Response.Results[0] received 'Bad (0x80000000), but Expected: Good (0x00000000); Would accept: UncertainInitialValue
(0x40920000)BadNotReadable (0x803a0000)BadUserAccessDenied (0x801f0000), when reading NodeId: ns=1;i=1043 (Value)

So please do not test that for variables that are not known what they mean.

TagsNo tags attached.
Attached Files
screenshot.jpg (391,754 bytes)
Files Affected

Activities

Paul Hunkar

2019-02-22 15:07

administrator   ~0009906

The Value status should not be checked by this script (the service result do need to be checked). we are just looking for the variable and Value attribute being available. The actual value of the value attribute does not matter.

Alexander Allmendinger

2019-02-23 22:21

developer   ~0009917

Script is now ignoring a Bad StatusCode of a variable while checking the address space.

Bernd Edlinger

2019-04-15 16:56

reporter   ~0010193

Still not working in 1.03.341.389

Alexander Allmendinger

2019-07-16 13:02

developer   ~0010490

The bad StatusCode can be at any index of the ReadResponse.Results which was missing. Now any Bad OperationResult should be accepted.

Paul Hunkar

2019-07-18 13:07

administrator   ~0010514

reviewed in CMP call

Issue History

Date Modified Username Field Change
2019-02-22 08:18 Bernd Edlinger New Issue
2019-02-22 14:53 Paul Hunkar Description Updated
2019-02-22 15:07 Paul Hunkar Note Added: 0009906
2019-02-22 15:07 Paul Hunkar Assigned To => Alexander Allmendinger
2019-02-22 15:07 Paul Hunkar Status new => assigned
2019-02-23 22:21 Alexander Allmendinger Status assigned => resolved
2019-02-23 22:21 Alexander Allmendinger Resolution open => fixed
2019-02-23 22:21 Alexander Allmendinger Fixed in Version => 1.03.341.384
2019-02-23 22:21 Alexander Allmendinger Note Added: 0009917
2019-04-15 16:56 Bernd Edlinger Status resolved => feedback
2019-04-15 16:56 Bernd Edlinger Resolution fixed => reopened
2019-04-15 16:56 Bernd Edlinger Note Added: 0010193
2019-04-15 19:36 Bernd Edlinger File Added: screenshot.jpg
2019-04-19 15:44 Paul Hunkar Status feedback => assigned
2019-07-16 13:02 Alexander Allmendinger Status assigned => resolved
2019-07-16 13:02 Alexander Allmendinger Resolution reopened => fixed
2019-07-16 13:02 Alexander Allmendinger Fixed in Version 1.03.341.384 => 1.03.341.390
2019-07-16 13:02 Alexander Allmendinger Note Added: 0010490
2019-07-18 13:07 Paul Hunkar Status resolved => closed
2019-07-18 13:07 Paul Hunkar Note Added: 0010514