| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010328 | Compliance Test Tool (CTT) Unified Architecture | 4 - Test Case Definition | public | 2025-05-13 12:25 | 2025-05-13 12:25 |
| Reporter | Jesper Palmér | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 1.04.09.398 | ||||
| Summary | 0010328: Should Attribute Write Values 006 accept BadOutOfRange? | ||||
| Description | Test case Attribute Services/Attribute Write Values/006.js "Write maximum value for each supported data-type" does not accept the statuscode BadOutOfRange, but test case 005.js "Write minimum value for each supported data-type" does accept statuscode BadOutOfRange. This causes test case 006 to fail for a DUT that does not support null bytestrings, but test case 005 passes. Attached image shows the packet that causes 006 to fail but when the same message is sent in test case 005 it passes. BadOutOfRange should be the correct response according to issue 0006341 (https://mantis.opcfoundation.org/view.php?id=6341): "BadOutOfRange is the expected StatusCode if the server does not support null values for a DataVariable of the DataType ByteString". Should this not be the same for test case 006? | ||||
| Steps To Reproduce | Run test case Attribute Services/Attribute Write Values/006.js with a dut that does not support NULL bytestrings. | ||||
| Tags | No tags attached. | ||||
| Files Affected | |||||
- Anonymous
