View Issue Details

IDProjectCategoryView StatusLast Update
0005603Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-06-03 16:56
ReporterOndrej Flek Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.04.09.394 
Target Version1.04.09.396Fixed in Version1.03.341.396 
Summary0005603: MaxStringLength test problem (Base Info Server Capabilities/006.js)
Description

In Step 1, CTT attempts to write a string of length MaxStringLength and expects the string to be accepted.
In Step 2, CTT is supposed to attempt to write a string of length MaxStringLength + 1, and expects the server to report the "OperationResults: BadOutOfRange" error. However, in reality, the length of the string CTT attempts to write in this test is different from MaxStringLength + 1 (typically shorter, thus the server accepts such string).

Steps To Reproduce
  1. The OPC UA Server under test has MaxStringLength = 1000.
  2. CTT attempts to write a string of length 1000, the Server accepts it.
  3. CTT attempts to write a string of length 5 (althought it is supposed to attempt to write a string of lenght 1001), and the Server accepts it too.
  4. CTT complains that the Server did not report the OperationResults: BadOutOfRange error
TagsNo tags attached.
Attached Files
MaxStringLength_error.jpg (468,202 bytes)
Files Affected

Relationships

related to 0005681 closedPaul Hunkar WriteService.GenerateString() is called with wrong parameter in script: generates string with wrong size 

Activities

Alexander Allmendinger

2020-05-28 09:04

developer   ~0012132

The read Value of the ServerCapabilities.MaxStringLength variable is not interpreted as a number and therefore the generation of the longer string in WriteService.GenerateString( 1 + stringLen ) does a ( 1 + stringLen.length) and therefore generates a string which has the number of characters of the length (e.g. 4 when having the limit set to 4096) + 1 which results in a string length of 5 in the generated string.
Now the limit is interpreted as a Number and the generation of the string works.

Paul Hunkar

2020-05-28 15:27

administrator   ~0012136

reviewed in CMP call

Issue History

Date Modified Username Field Change
2020-04-30 12:25 Ondrej Flek New Issue
2020-04-30 12:25 Ondrej Flek File Added: MaxStringLength_error.jpg
2020-04-30 14:09 Paul Hunkar Assigned To => Alexander Allmendinger
2020-04-30 14:09 Paul Hunkar Status new => assigned
2020-05-28 09:04 Alexander Allmendinger Status assigned => resolved
2020-05-28 09:04 Alexander Allmendinger Resolution open => fixed
2020-05-28 09:04 Alexander Allmendinger Fixed in Version => 1.03.341.396
2020-05-28 09:04 Alexander Allmendinger Note Added: 0012132
2020-05-28 15:26 Paul Hunkar Target Version => 1.04.09.396
2020-05-28 15:27 Paul Hunkar Status resolved => closed
2020-05-28 15:27 Paul Hunkar Note Added: 0012136
2020-06-03 16:56 Paul Hunkar Relationship added related to 0005681