In this script WriteService.GenerateString() is called with
WriteService.GenerateString( stringLen ) instead of WriteService.GenerateString({length: stringLen})

maintree\Base Information\Base Info Server Capabilities\Test Cases\006.js

in this case the WriteService.GenerateString() will generate a string with the length of the parameter as a string.
for example: WriteService.GenerateString( 1 + stringLen ) with stringLen (as type string) of 254 will generate a string with length 4 (length of "1254" because stringLen is not a number)

Searching for "WriteService.GenerateString" will find other possible wrong occurrences.

posssible patch for maintree\Base Information\Base Info Server Capabilities\Test Cases\006.js:

diff --git a/maintree/Base Information/Base Info Server Capabilities/Test Cases/006.js b/maintree/Base Information/Base Info Server Capabilities/Test Cases/006.js
--- a/maintree/Base Information/Base Info Server Capabilities/Test Cases/006.js
+++ b/maintree/Base Information/Base Info Server Capabilities/Test Cases/006.js
@@ -22,7 +22,8 @@ function test() {
var realValue = itemMaxLen.Value.Value;

 // check the setting and set a bound if necessary

• var stringLen = itemMaxLen.Value.Value;
• var stringLen = itemMaxLen.Value.Value.toUInt32();

• if( stringLen == 0 ) {
  addWarning( "MaxStringLength set to 0 (meaning 'no limit'). It should be set to a more realistic value. OperationLimit will be limited to this value." );
  stringLen = MAX_ALLOWED_SIZE;
  @@ -36,7 +37,7 @@ function test() {
  itemString.InitialValue = itemString.Value.Value.clone();

  // now to write a string whose length matches the setting

• itemString.Value.Value.setString( WriteService.GenerateString( stringLen ) );

• itemString.Value.Value.setString( WriteService.GenerateString({length: stringLen}));
  addLog( "Specified string of length: " + itemString.Value.Value.toString().length );
  if( !WriteHelper.Execute( { NodesToWrite: itemString, ReadVerification: false } ) ) {
  // In testing we've found that some servers will crash or become none-too-reliable. Terminate channel and recreate.
  @@ -47,7 +48,7 @@ function test() {

  // can we exceed the count?
  if (stringLen != Constants.UInt32_Max && stringLen != MAX_ALLOWED_SIZE ) {

• itemString.Value.Value.setString( WriteService.GenerateString( 1 + stringLen ) );
• itemString.Value.Value.setString( WriteService.GenerateString({ length: 1 + stringLen} ));
  if( !WriteHelper.Execute( { NodesToWrite: itemString, OperationResults: new ExpectedAndAcceptedResults( [ StatusCode.BadOutOfRange, StatusCode.BadEncodingLimitsExceeded ] ), ServiceResult: new ExpectedAndAcceptedResults( [ StatusCode.Good, StatusCode.BadEncodingLimitsExceeded ] ), ReadVerification: false } ) ) {
  // In testing we've found that some servers will crash or become none-too-reliable. Terminate channel and recreate.
  Test.Disconnect();
  --