Log In
Home
10/13/2017
Offline
In e.g. Attribute Services - Attribute Write Values - 001, the test tries to write an attribute and accepts StatusCode.Good and StatusCode.BadWriteNotSupported.
However, in the specification, part 3 (release 1.03) table 3, it is stated, for ValueForVariableType, that "It does not apply for Variables since this is handled by the AccessLevel and UserAccessLevel Attributes for the Variable. For Variables this bit shall be set to 0."
Doesn't this mean that the accepted status code in addition to Good should be BadUserAccessDenied?
Also, in the clean up of the test revertToOriginalValues(), not so logically placed in initialize.js
, no ExpectedAndAcceptedResults arguments are included so it tries to revert a value that hasn't been changed and isn't writable.
07/05/2017
Offline
Some additional information on what you are asking:
Table 3 Part 3 - Bit mask for WriteMask and UserWriteMask describe what the bits in the writemask/userwritemask apply to. there is no bit for value, since the value is handle separately. The ValueForVariableType bit is if the value field is in a VariableType definition - i.e. what it is stating is that this bit is only for a VariableType not a Variable.
The value field is only governed by the fields described in table 8 - i.e. AccessLevel and UserAccessLevel
So an Access level of read is not a user access level restriction, it is just not writeable. UserAccessdenied imply that some user might be able to write, but a AccessLevel of ReadOnly say no user will ever be able to write this value. A should be told that the value is Not writeable (by anyone).
What version of the CTT are you using? then we can better investigate this issue with regard to cleanup.
Paul
05/24/2017
Offline
paul.hunkar@opcfoundation.org said
What version of the CTT are you using? then we can better investigate this issue with regard to cleanup.
Paul
Hi,
Thanks for the explanation. We are using the latest release, version 1.02.336.273.
Br, Jonas.
1 Guest(s)
Usage Policy