6.0.2 - Inconsistent use of bool returning element property
Posted: Tue Aug 30, 2016 9:44 pm
Ranorex 6.0.2
Windows 10 Pro
When using Spy, boolean properties display "True" or "False", but when getting the value in user-code several of them return a string representation of the boolean value instead of the expected raw boolean, while the rest return a raw boolean value, as expected.
For example, a web input tag element's "Disabled" property in Ranorex returns a string "True" or "False", but the "Enabled" property returns a boolean true/false. The "Checked" value is also returned as a string "True" or "False", but in HTML, the actual attribute has no associated value and is just an attribute such as "<input checked>", while in XHTML it is "<input checked='checked'>" (see http://www.w3schools.com/tags/att_input_checked.asp for usage). Since these values are being generated, instantiated, or populated by Ranorex anyway, this appears to be a consistency issue with how Ranorex treats these types of values.
All properties whose values are generated by Ranorex and return boolean string values should instead return raw boolean values as this is more consistent with expected use and logical structure. If the user needs a string version, they should use the boolean's ToString() method, or it should be implicitly called by Ranorex in the back-end as with other object types.
Windows 10 Pro
When using Spy, boolean properties display "True" or "False", but when getting the value in user-code several of them return a string representation of the boolean value instead of the expected raw boolean, while the rest return a raw boolean value, as expected.
For example, a web input tag element's "Disabled" property in Ranorex returns a string "True" or "False", but the "Enabled" property returns a boolean true/false. The "Checked" value is also returned as a string "True" or "False", but in HTML, the actual attribute has no associated value and is just an attribute such as "<input checked>", while in XHTML it is "<input checked='checked'>" (see http://www.w3schools.com/tags/att_input_checked.asp for usage). Since these values are being generated, instantiated, or populated by Ranorex anyway, this appears to be a consistency issue with how Ranorex treats these types of values.
All properties whose values are generated by Ranorex and return boolean string values should instead return raw boolean values as this is more consistent with expected use and logical structure. If the user needs a string version, they should use the boolean's ToString() method, or it should be implicitly called by Ranorex in the back-end as with other object types.