It seems to me like the following step should take the basic javascript/json data types and not the JVM datatypes. From an outside (business or engineer) when writing test steps you might want to check whether a value is a "number" but according to JSON there is no differentiation based on length instead it's simply a "number" type.
Current:
And response contains property "timeMs" of type "bigdecimal"
Proposal:
And response contains property "timeMs" of type "number"
Hi, thanks for mentioning. We had that at early stages, then somehow switched to JVM types, because of some issues. I'll recheck this and come back with status update
It seems to me like the following step should take the basic javascript/json data types and not the JVM datatypes. From an outside (business or engineer) when writing test steps you might want to check whether a value is a "number" but according to JSON there is no differentiation based on length instead it's simply a "number" type.
Current:
Proposal:
Full list of accepted types based on http://www.w3schools.com/js/js_datatypes.asp :