Forum Discussion

BrandonFowler's avatar
BrandonFowler
Occasional Contributor
11 days ago

Issue with 'Keys' Operation

I just updated to Chrome version 140.xx and the keys operation has stopped working like it did before. When trying to enter text into a text box it targets the tab groups button in the upper left hand corner of the browser, beneath the 'go back' button. The test seems to work if I remap the object and replace it with the 'Set Text' operation. I am running on the patched version of TestComplete 15.76 and I am waiting to upgrade to the latest release. I am wondering if anyone else is having this issue with 15.77?

Thanks for your time!

11 Replies

  • BrandonFowler​ Hassan_Ballan​ rraghvani​ wsgarcia​ HirendraSingh​ gdemaret​ 

    We can confirm that there is an issue with Keys operation. It is under investigation.

    With Web objects, from what we know this started after the major Chromium upgrade (v139).
    Chromium deprecated V2 manifest and migrated to V3.

    This is not linked to any TC version. All the TC versions will have this issue if you are using the operation in Web objects.

    However the issue does not exist in all web objects. Please see the video attached here.
    In the video, the test behaves as expected. It enters Page Up, Page Down, text, Enter key without any issues. This was tested in TC 15.77, Edge v140.

    We are gathering more information from our users for investigation.

  • wsgarcia's avatar
    wsgarcia
    Occasional Contributor

    I ran into this issue with Edge running on a specific OS. On our test servers we run MS Server 2019 and this is causing an issue with using the Keys method. I've been forced to run on Chrome only for now until we can update the servers. 
    Not sure what OS your using or if this is relevant to your issue, but thought it might help. 

    • BrandonFowler's avatar
      BrandonFowler
      Occasional Contributor

      Issue is occurring on MS Server 2022 and it's also happening locally on Windows 11. Currently working with Smart Bear Support as they're apparently unable to reproduce this issue on their end. This was one of my suspicions as well so it's very helpful. Thanks!

  • HirendraSingh's avatar
    HirendraSingh
    Occasional Contributor

    Same issue was reported by me in 15.74 version of TestComplete it sometime work and sometimes not, so as a workaround I change all my Keys method to use with Sys.Desktop operation and that work fine till now. I guess TestComplete quality team does not verify all its methods so same type of issues appears multiple after one or the other update.

    • rraghvani's avatar
      rraghvani
      Icon for Champion Level 3 rankChampion Level 3

      If you downgrade TC, the you will have the issue of the following -

      Chrome flashing after update v.139 on Windows 11. Fixed a critical issue where Google Chrome would continuously flash or refresh during playback on Windows 11 after updating to Chrome version 139. This caused unstable testing behavior and UI element interaction failures.

      This is the same sort of response that SmartBear Support give, not realising that there's issues in the previous version of TC too!

       

      • BrandonFowler's avatar
        BrandonFowler
        Occasional Contributor

        Well if you're able to downgrade to Chrome 138 and downgrade TC, then you could avoid both issues. My company simply does not allow me to downgrade chrome on their machine for security concerns.

    • BrandonFowler's avatar
      BrandonFowler
      Occasional Contributor

      Ah, you're right I did not read the OP's replies to the comments. Looks like this is not just a me issue then. I have opened a Ticket with Smart Bear. Downgrading Chrome is not an option for me here.