ContributionsMost RecentMost LikesSolutionsRe: ClickItem is selecting each drop-down item in latest TestComplete instead of required itemNope, don't have a solution yet, and only happening in Chrome for me, Tried it one Edge and it was fine.ClickItem is selecting each drop-down item in latest TestComplete instead of required item Just wondering if anyone else has encountered this in latest version of TestComplete. 15.52.2.7 I have keyword test(s), where for a drop-down control I am using ClickItem to select a specific entry. Previous versions of TestComplete just selected the specified item immediately. Now test complete is selecting each item in the drop-down until it finds the specified item. If the list is too long, it selects items until a timeout occurs even if the specified item has not yet been found. This is a problem as some of the dropdown items trigger pop ups and add or remove controls from the screen when selected. Meaning my test is now encountering unexpected/missing controls. SolvedRe: Problems with TestComplete 15 and Chrome 113 So I have also discovered this issue after a recent system upgrade. Chrome version 113 is not compatible with the SmartBear extension. I have tried downloading and installing Chrome version 105 and disabling updates by using information from https://www.chromium.org/administrators/turning-off-auto-updates/ and https://support.smartbear.com/testcomplete/docs/app-testing/web/general/preparing-browsers/chrome.html I added the two new reg keys suggested (one by each article) with no success. Chrome still updates automatically to version 113. I am not connected to a workplace network so the ADM group policy option doesn't apply to me. Does anyone know of any other methods for preventing Chrome from auto-updating? Otherwise Chrome cannot be currently used with TestComplete and will be useless until there is a patch. Re: Object is not detected by TestComplete. Can it be made detectable? Resolved it myself by editing the HTML of the loaded page. The undetected object was a <span>, which was empty, but had classes assigned for CSS formatting. When I added a text character to it, this then made the control detectable and I mapped it. Removed the added text after mapping and control remained detectable to TestComplete. Re: Object is not detected by TestComplete. Can it be made detectable? Just in relation to this point. The sibling element span > span.rf-layout-row > span.rf-message-red.rf-cell-label.rf-column-label-xl can be detected by TestComplete. Would this be possible if there was an iFrame? I'm assuming both the siblings, including the undetectable one, would be affected by the iFrame. So if one is detectable and one not does that indicate that there is no iFrame, and something else is the issue? Re: Object is not detected by TestComplete. Can it be made detectable? Good question and I have no idea, will have to ask the Devs and if it is the iFrame issue I will check out the link. Thanks for the suggestion👍👍 Object is not detected by TestComplete. Can it be made detectable? Hi everyone, I am trying to understand why I can't detect and therefore map a particular object in my tested web application. Screenshot is attached of the element being inspected. Anyone know why it's not being detected by TestComplete/ How the developers could change it to make it detectable? Thanks Tom. Re: WaitProperty not detecting that property is not at expected value Ok, didn't realise that was the case. I thought all test steps would cause the test to stop if they couldn't be completed. Thanks. Re: WaitProperty not detecting that property is not at expected value Thanks for that, I thought that selecting the property as per my original screenshot would just select the "Enabled" property. Didn't realise that it was looking for a property named with the full alias. WaitProperty not detecting that property is not at expected value Hi all, I have a WaitProperty step in my keyword test, I am trying to check if a button is enabled or not before the test proceeds, so have selected the button as the object and "Enabled" property as the value to check, with the Property value set to True. Issue is that when I run the test, with the button disabled, the test does not stop on the WaitProperty operation, so appears to not be checking the Enabled status of the button. See screenshots for details Solved