Hi Benoit,
Your idea with performance measuring is really a great one. I thought about it after I wrote my initial reply to this thread but did not try it yet. 😞
One more idea:
Instead of
switch(value.toLowerCase().trim()){
case "true" :
case "yes" :
case "on" :
case "1" :
case "oui" :
case "vrai" :
case "checked" :
return true;
which uses several 'case'-s without return (I understand the reason but I bet you know;) that this is not recommended technique), you may consider this:
var strTrueList = 'true|yes|on|1|oui|vrai|checked';
var strFalseList = 'false|no|off|0|non|faux|unchecked|'; // explicit null is not supported
switch (true)
case aqObject.CompareProperty(value.trim(), cmpIn, strTrueList, false, lmNone) :
return true;
case aqObject.CompareProperty(value.trim(), cmpIn, strFalseList, false, lmNone) :
return false;
default:
return Boolean(value);
// or just
var strTrueList = 'true|yes|on|1|oui|vrai|checked';
if (aqObject.CompareProperty(value.trim(), cmpIn, strTrueList, false, lmNone))
return true;
else
return false;
(Though not sure if it is faster than native JScript code.)
P.S.
> less dependant on TC objects
My personal preference is opposite: if some TC object provides functionality that I need then I will use this object in favor of the native functionality provided by the scripting language that is used for the project.
The reason for this is that it is much more easy to port the code that uses TC objects between projects based on different scripting languages.
Sure, if one is an employee for the project that lasts for many years, the above might be irrelevant for him/her. But if one works, say, as a contractor/consultant, then the use of TC objects makes it faster and with less chance of an error to move generic/library test code between different projects.
P.P.S.
> - on table/objetct type, different results, mine return "true", yours "false" 😔
I tried to evaluate
Boolean({obj : 1})
and
Boolean({obj : 0})
in TestComplete's Evaluate dialog. Result in both cases was True which makes me think that in your case True was returned not because obj property was set to 1, but because the whole argument for the Boolean() function was not null/empty and thus was evaluated to boolean True. (The same relates to the NaN argument.)
Regards,
/Alex [Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
================================
