We are wondering why your initial values are such large numbers?

we are proposing no changes, since a failed test is always reviewed by the tester and they would notice the very large initial value and just use a different double with a smaller value for the test.

The variables of our test server are generated randomly.
If your test can´t handle large numbers, it sould change them before or have an better description.

This is also an issue with Int64 and UInt64. After the execution ofelse arrayWriteValues[w] = b[w] + args.Increment; on large values, the arrayWriteValues[w] is the same as b[w].

I am using the OPC UA ReferenceNodeManager (https://github.com/OPCFoundation/UA-.NETStandard/blob/a147eb55c5cf587c675d5e7811207df178ec66f5/Applications/Quickstarts.Servers/ReferenceServer/ReferenceNodeManager.cs) to create the CTT nodes, and this populates large values inside Int64 and UInt64. In other words the official reference server cannot pass the CTT.

In the linked mantis (7992) this problem has already been addressed in some places of the increcment function.
The hard coded max value has now been added as constant.
If a Double, Duration, Int64 or UInt64 exceeds that number as a Scalar, in an Array or multi dimensional array, it will be set to 0.

reviewed issue (QT does not support double and int 64 thus the work around) - agreed to changes and closed issue