View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006191Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-10-29 12:492021-04-01 14:33
ReporterMaximilian Assigned ToSebastian Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformDesktopOSWindows 10OS Version1903
Product Version1.04.09.396 
Fixed in Version1.03.341.397 
Summary0006191: AddressSpaceModel/UserWirteAccess/Err-004.js writes to UserAccessLevel instead of Value attribute
Description

In line 36 the WriteHelper uses item as NodeToWrite to write to the node and check whether the expected StatusCodes respond.
But the AttributeId of the item is still 18(UserAccessLevel). In this case the test tries to write to the UserAccessLevel which allways lead to an BadNotWriteable StatusCode, because the UserAccessLevel attribute should never be writeable (unless the UserWriteMask allows this, which is not the case).

The issue starts after line 16("read the node"). The code here is incomplete, because the value will never read. So in line 36 the script can´t "just write back the same value..." because it never read one and the AttributeId in the item is still UserAccessLevel instead of Value.

In this case the test will allwas ends in a Warning state since the StatusCode will never be BadUserAccessDenied.

Steps To Reproduce

Just use script as expected

TagsNo tags attached.
Attached Files
AddressSpaceUserWirteAccessErr-004.png (109,479 bytes)   
AddressSpaceUserWirteAccessErr-004.png (109,479 bytes)   
Files Affected

Activities

Paul Hunkar

2020-10-29 14:18

administrator   ~0013089

The script should be updated to actually write to the value attribute (not the UserAccessLevel). Note: the spirt of the test as it is written is still ok - since that attribute is never writeable .

Maximilian

2020-10-29 15:27

reporter   ~0013091

For me the description sounds like this test should test that the UserAccessLevel is correct an working. At the moment the test will always show a warning status, even if everything is correct.

Sebastian Allmendinger

2020-10-30 09:29

developer   ~0013093

The script has been investigated and has been updated.
There was an incorrect check, so that the script was not skipped if the UserAccessLevel is not CurrentRead (line 25).
The AttributeId is now set to the value attribute before issue the write. In addition the current value is read in advance, so that the write request contains a valid value.

If the server returns BadNotWritable, the script still throws a warning because BadUserAccessDenied is expected.

Paul Hunkar

2021-04-01 14:33

administrator   ~0014144

reviewed in CMP call , agreed to changes and closed

Issue History

Date Modified Username Field Change
2020-10-29 12:49 Maximilian New Issue
2020-10-29 12:49 Maximilian File Added: AddressSpaceUserWirteAccessErr-004.png
2020-10-29 14:16 Paul Hunkar Assigned To => Alexander Allmendinger
2020-10-29 14:16 Paul Hunkar Status new => assigned
2020-10-29 14:18 Paul Hunkar Note Added: 0013089
2020-10-29 15:27 Maximilian Note Added: 0013091
2020-10-30 09:29 Sebastian Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2020-10-30 09:29 Sebastian Allmendinger Status assigned => resolved
2020-10-30 09:29 Sebastian Allmendinger Resolution open => fixed
2020-10-30 09:29 Sebastian Allmendinger Fixed in Version => 1.03.341.397
2020-10-30 09:29 Sebastian Allmendinger Note Added: 0013093
2021-04-01 14:33 Paul Hunkar Status resolved => closed
2021-04-01 14:33 Paul Hunkar Note Added: 0014144