View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005665Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-05-26 12:042020-06-03 17:33
ReporterAlin Moldovean Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.04.09.395 
Summary0005665: Inconsistent error codes for DataEncoding validation
Description

Inconsistent error codes for DataEncoding validation

Test "Attribute Read\Err-017.js" expects error code BadDataEncodingInvalid for DataEncoding with Name = "Xml" and NamespaceIndex = 0

While test "Attribute Alternate Encoding\Err.004.js" expects error code BadDataEncodingUnsupported for DataEncoding with Name = "modbus" and NamespaceIndex = 0

The only difference is that one tests performs a Read request and the other a CreateMonitoredItems.

Normally a server has the same validation method of a ReadValueId for both Read and CreateMonitoredItems calls, so one of these tests will fail.
I think BadDataEncodingInvalid should be the expected error code also for "Attribute Alternate Encoding\Err.004.js"

Steps To Reproduce

Run tests "Attribute Read\Err-017.js" and "Attribute Alternate Encoding\Err.004.js"

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2020-05-27 17:21

administrator   ~0012130

The read test, is specific test that is trying to request an alternate encoding for something that is not allowed to have an alternate encoding (only value attribute with a datatype of structure are allowed to have an alternate encoding) - this test is requesting an alternate encoding for a boolean - which is an invalid request, not an invalid encoding. The expected errors is correct

Paul Hunkar

2020-05-27 17:23

administrator   ~0012131

We feel this test is correct - do you have alternate encoding available for structured variables? (is it XML)?

Alin Moldovean

2020-05-28 11:37

reporter   ~0012133

Ok, so BadDataEncodingUnsupported error should be returned for Value attribute of nodes with structured data types in case the encoding is not supported by the server.
For other cases like when DataEncoding cannot be applied or it has no meaning, a BadDataEncodingInvalid error code should be used.

Thank you!

Paul Hunkar

2020-06-03 17:33

administrator   ~0012175

reviewed in CMP Call

Issue History

Date Modified Username Field Change
2020-05-26 12:04 Alin Moldovean New Issue
2020-05-27 17:21 Paul Hunkar Note Added: 0012130
2020-05-27 17:23 Paul Hunkar Assigned To => Paul Hunkar
2020-05-27 17:23 Paul Hunkar Status new => feedback
2020-05-27 17:23 Paul Hunkar Note Added: 0012131
2020-05-28 11:37 Alin Moldovean Note Added: 0012133
2020-05-28 11:37 Alin Moldovean Status feedback => assigned
2020-05-28 11:37 Alin Moldovean Status assigned => resolved
2020-05-28 11:37 Alin Moldovean Resolution open => fixed
2020-06-03 17:33 Paul Hunkar Resolution fixed => no change required
2020-06-03 17:33 Paul Hunkar Status resolved => closed
2020-06-03 17:33 Paul Hunkar Note Added: 0012175