Agreed

this also effects ByteString, DateTime, Duration, ..., These datatypes could also be limited in range by the used data sources/device.
For example I can not test ByteString (has as fixed length) and DateTime (year range 1990-2169) because the test scripts do not consider the fixed ranges.

An alternative solution could be to extend the Settings in /Server Test/NodeIds/Static/All Profiles/Scalar/ with a input box for min/max value or min/max lenght for this kind of variables.

This issue is about The MaxstringLength property which is defined in the OPC Specification and that we should use it instead of an CTT setting. This issue should not be extended for other unrelated topic (OPC already has defined rules for datetime, which I believe tests are already following), If other issues exist for other types enter separate issues for them, The CTT just follows what the specification says - adding configuration setting that restrict testing is not appropriate, A Server needs to conform to what is in the specification.

If a new string value is generated, the CTT honors the MaxStringLength/MaxCharLength property of the node if available.
If not, it uses the value of the MaxStringLength node of the ServerCapablities object.
If this optional property is not provided, a length of 1000000 is used.

The test script 'Base Info Server Capabilties / 006' that test the MaxStringLength of the server, is skipped if the configured node provides a MaxStringLength property that is smaller than the value of the MaxStringLength node in the ServerCapabilities object.

Reviewed updated , approved and closed in meeting