Validation issue when properties are int or date
We're using a lot of project properties as variables in our test steps
When a property is used in an integer or data field
like this ${Properties#aNumber} the validator says it's the wrong datatype. It does this in both form and xml view.
The webservice call itself is fine, it's just the validation that fails
I assume it's because all properties are really strings and the validator expects the right datatype. I suggest extending the validator with a parseDat and a parseInt if it can't find the expected datatype
When a property is used in an integer or data field
like this ${Properties#aNumber} the validator says it's the wrong datatype. It does this in both form and xml view.
The webservice call itself is fine, it's just the validation that fails
I assume it's because all properties are really strings and the validator expects the right datatype. I suggest extending the validator with a parseDat and a parseInt if it can't find the expected datatype
