Server Receives Message with Header Value gives false positive

[harshm]

I was running the acceptance test and came across this when I ran the following Test case after modifiying the value for header:reserved:0xff to header:reserved:0xaa

• Atest
  • Default Values
    • Default values for header fields

Here's the Test Case with the modified Keyword

"""
Client sends    Header value ExampleMessage
${msg}= Server receives    Header value 0xAA ExampleMessage
Should be equal ${msg._header.reserved.hex} 0xff
"""

Here's the Modified Keyword Header value 0xAA ExampleMessage

"""
Value ExampleMessage**      
Value    header:reserved    0xaa
"""   

With the Keyword Modified above, the test case should have failed. It seems like specifying the header value for reserved is making no effect.

My Apologies if I am not understanding this correctly.

Please correct me if I am wrong.

Thanks, Harsh

[jussimalinen]

Are you running this on the latest version? I tried this change you mention and the validation works. I get error: FAIL Value of field Example.reserved does not match 0xff!=0xaa

If you can provide a example test that I could run, where this fails for you (copy and past to a a gist is enough), I could verify what goes wrong.