Hi,
There's a potential bug I found in latest TestComplete version (15.72.60.7), where the "Keys" method is not entering "*" in the text field, the old version of TestComplete was fine. Also, I tried entering "*" using "SetText" method, and it works fine. Because of this some of my test cases are failing.
Thanks,
Hina
Champion Level 3I found it. I don't think there is anything there to help you however. 🫤 The last post seems to be left at a problem with 15.72.
Problem entering character * | SmartBear Community
Champion Level 3Yes try using the [NumAsterisk] instead of *, it may get you going.
Hi Hassan,
Thank you for your reply. [NumAsterisk] worked!! But I have opened a support ticket to get this fixed. I have couple of test cases using *, it's going to be an effort to update all of them.
Champion Level 3I saw a similar post about this. Let me see if I can find it.
Champion Level 3Out of curiosity, what would happen if you added the * to a variable and concatenate this into the string or used a string literal format instead? Now I am just fishing for what might work to guess at what could be causing the problem. 🎣🐟🎣
https://www.w3schools.com/js/js_string_templates.asp
someObj.Keys(`* is not working.`);
someObj.Keys(`'${"*"}' is not working.`);
Champion Level 3That's good to know. That is typically used to send specifically the number pad * to an object. Yeah, it doesn't make sense to refactor tests to work around something that should work the way it is intended.
Champion Level 3It's documented here https://support.smartbear.com/testcomplete/docs/reference/test-objects/members/common-for-sys-desktop-pda/keys-method-sys-desktop-object.html However, doing TestObj.Keys("*") could have been a bug itself!
