courtenayp
Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Alert/Confirm object message property is now blank using Chrome 114/116 and TC 15.54
hi this doesnt solve my issue as i can see you are using the new "label" child object of the alert/confirm that now appears to be there, there are still other parts of text within theses objects that is totally unrecognisable. anyway, after also jumping on the post about the OK buttons not working and that is still not resolved with chrome 116 and TC15.55 i have reverted back to my old version of chrome, because im wasting time trying to work out a combination that works again - it seems ok with old chrome and TC15.53 (i tried TC15.55 and that version does not recognise alert/confirm object at all going back to chrome 106, and i tried TC15.54 and that version does not recognise all alert/confrim message content + has a child "label" object now being added which contains some of the message content of the alert/confirm object) to summarise (all below using chrome 106, also 114 seems fine) TC15.53 - recognises the alert/confirm fine including the text within it under a Message property TC15.54/55 - recognises the alert/confirm fine, but only recognises part of the text in it under a NEW child object with ObjectIdentifier "Message" and ObjectType "Label" Below screenshots show the TC15.55 2x objects found with label child object only showing irst line of confirm dialog, and TC15.53 a single alert object with message property containing the ALL the text there is clearly a change in TC15.54426Views1like0CommentsRe: Click doesn't work on Chrome popup
edited after testing: ive reverted back again to much earlier version of chrome to resolve my issue, below is summary from my other discussion: to summarise (all below using chrome 106, have now also tested 114 which is fine inc click OK) TC15.53 - recognises the alert/confirm fine including the text within it under a Message property and the OK button TC15.54/55 - recognises the alert/confirm fine, but only recognises part of the text in it under a NEW child object with ObjectIdentifier "Message" and ObjectType "Label" seems like an issue with changes in TC .54 to me...224Views0likes0CommentsRe: Alert/Confirm object message property is now blank using Chrome 114/116 and TC 15.54
Hi, You are showing in the above screen shot, the Alert.Label message property, not the Alert message property which is the level at which it was previously picking up the Alert's message content. I am using TC 15.54 as mentioned above with Chrome 114 which it says it supports. I was previously on old versions of both TC and Chrome and did not upgrade for ages because there are always issues with chrome - however since it said this version combination should work i proceeded with the upgrade. I have changed some of my mappings to this apparent new structure, its not worth the time working out the root cause. I will just have to change them all at each point my test is now failing, and hope the structure does not change again. I will also need to upgrade to TC 15.55 it seems now because there is another issue which already has a discussion where the alert OK buttons are now not clickable - so hopefully this doesnt introduce even more issues.532Views0likes1CommentAlert/Confirm object message property is now blank using Chrome 114/116 and TC 15.54
Have just upgraded to latest TC, it now appears that all the message property content of alert/confirm objects in chrome are picked up by TC as blank instead of the previous message content that was mapped. The message can now only be picked up by mapping another child object to all existing alert/confirm objects as a Label object. This is the case for chrome 114 and 116. 1. do we have to update all of our previously mapped alerts with message property to now have a child label object, or 2. can we get back the mapping of message content directly on the alert/confirm objects editing to add, on further look at other examples, on some alerts, there is now the additional "label" message object, but also some of the text remains inside the parent alert object and is not accessible now via that object's message property (As it is blank)676Views0likes6CommentsRe: Chrome 107 and Alerts
has any one got this working!? i just updated to the latest 15.49 and chrome 111, BROKEN. downgraded back to chrome106 BROKEN, downgraded to TC15.48 BROKEN.... wont recognise Confirm popups now im in the process of working out what TC version i was on where i had it working chrome 106 What on earth this is such a waste of time! 😶153Views0likes0CommentsRe: Chrome 107 and Alerts
yeah wow ok - i did think surely they could be more "up to date" with latest chrome versions, as this issue with alerts always seems to come up - one would think you would monitor and test out that one thing straight away each chrome release... sounds like its doable if others can! I have considered if changing over product is a good idea.. I'm stuck in the "i have SO many test scripts in this product I probably cant change over" scenario though i think - my tests are extremely comprehensive and across both web and desktop etc.. seems like a mammoth task to switch! Other than this constant Chrome thing though, over the past few years there have definitely been less bugs with TC so thats a positive...804Views0likes0CommentsRe: Chrome 107 and Alerts
Update from me incase this helps anyone else in the meantime, apparently latest TC version will support alerts up to Chrome 106, I have manually reverted to Chrome 106 and turned off auto updates. First run appears TC can now recognise the alert objects. I was told "mainly all alerts and js popups are broken in chrome 107 and above...they are still trying to fix this issue... next update of testcomplete".819Views0likes0CommentsRe: Chrome 107 and Alerts
Hi - just tagging along here - i was on older versions to get around this issue, just paid for new testcomplete licenses thinking an upgrade will solve this issue - seems not. Product is completely useless without this issue resolved - I have also submitted a support request in hope there is some sort of patch available if you ask directly!? There used to be patches for this issue for versions of chrome...considering the latest one is for Chrome 99, you would think there might be more now that its Chrome 108........832Views3likes0CommentsRe: Unable to Select Dropdown value in latest version of Testcomplete and TestExecute Version: 15.40.421
Hi All, I am also suddenly having this issue on multiple drop-down selections in my tests since updating. I have the same error as above, although in my screenshot i can see the drop down is open but then it seems like TestComplete/Execute just doesn't register that its open ... I am now on Chrome 100 (after forced update last week) however i think the issue was still there prior to that, i just didnt realise it was an issue across my entire test suite until now. It seems to happen randomly and not on all drop down selection actions in my tests...575Views0likes0CommentsRe: SessionCreator failed to query the ItcSessionCreator interface - TestComplete 15
Hi, thank you for the responses, i think as Krzych has mentioned, i had issues between 14 and 15 upgrade, along with some possible windows configs that had changed during updates. SessionCreator now works as before. Regards, Courtenay514Views0likes0Comments