Discussed in UA Telcon today and decided:

Because EU range is Mandatory and EU Range is a subset of the Instrument Range, then the proper test is for EU Range, not Instrument Range. Part 8 says this about clients writing values outside the EU Range:

"Similarly a Client may attempt to write a value that is outside of this range back to the server. The exact behaviour (accept, reject, clamp, etc.) in this case is Server-dependent. However, in general Servers shall be prepared to handle this. "

Therefore test cases need to be developed to accept all of the allowed behaviors (accept, reject and clamp).

The fix implies that we need to fix EURange testing, but EURange test is correct and complete in all cases. The original Mantis issues (On part 8) was with regard to Instrument Range testing, but the resolution to that issue dos not describe Instrument range - so unless additional information is provided this is a no fix

Script is now allowing all OperationResults which are valid for the EURange

MantisIssue has been kept open because of the continued discussion and then forgotten to be marked as resolved. It already has been part of 1.03.341.390 and the test cases are reflecting the change since version 1.03.341.396.

reviewed in CMP call