Forum Discussion

jorgesimoes1983's avatar
jorgesimoes1983
Regular Contributor
11 years ago

Windows 8.1 related problem? Keys Method?

Hi! In the past days I've been trying windows 8.1 and testcomplete, it happens that while running my project I've been getting some errors.



I use Keys method to write the application urls in IE, and it has been "eating" some letters from the urls, for instance:



I have the url http://www.google.com, the method only writes http://www.googl.com



The trimmed letter is never the same... it "eats" the letter randomly...



Do you have any clue of what the problem might be?

7 Replies

  • jorgesimoes1983's avatar
    jorgesimoes1983
    Regular Contributor
    I managed to run the project successfully, the previous problem was happening because of settings.
  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)

    Hi Jorge,


     


    As far as I remember, IE 11 is installed on Windows 8.1. The behavior you describe may be related to the fact that TestComplete 9 officially supports neither this browser version nor the Windows version. The support of all of these will be added to TestComplete 10 that is in the beta state now.


    Could you please report this issue to our TestComplete Support team so that they could analyze whether it's reproduced in TestComplete 10?

  • jorgesimoes1983's avatar
    jorgesimoes1983
    Regular Contributor
    Thank you Tanya.

    I kept trying, and got different results in different machines.

    One seems to be ok, in the other got the errors reported.

    I'll keep testing and give further notice.
  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    Hi Jorge,



    It might help others if you mention what change to what settings helped to solve the problem...
  • jorgesimoes1983's avatar
    jorgesimoes1983
    Regular Contributor
    We have two different machines, one works fine (with the usual testcomplete recommended settings "preparing testcomplete for the web" the other I haven't fixed the issue yet. I'll share the problem and solution if I come across it.
  • damians1987's avatar
    damians1987
    Occasional Contributor

    Hi,

     

    I have the same problem with TestComplete 10.6 and IE11. Simple example of the test:

     

    function Test1()

    {

      var textarea;

      Browsers.Item(btIexplorer).Navigate("http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea");

      textarea = Aliases.browser.pageWwwW3schoolsComTagsTryitAspF.frameIframeresult.textarea;

      textarea.Click(264, 54);

      textarea.Keys("[Enter]the quick brown fox jumps over the lazy dog");

      textarea.Keys("[Enter]the quick brown fox jumps over the lazy dog");

    }

     

    results in textarea being populated with the following:

     

    he quick brown fox jumps over the lazy dog

    the quick brown fox jumps over the lazy do

     

    some letters are missing. There is NO error or suspicious message logged. The only additional information I get is the following:

     

    '[Enter]the quick brown fox jumps over the lazy dog' was sent as a keyboard input to the following window or control.

    Tested object:
    Aliases.browser.pageWwwW3schoolsComTagsTryitAspF.frameIframeresult.textarea
    (Sys.Browser("iexplore").Page("http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea").Panel(0).Panel(1).Panel(0).Panel(1).Frame("iframeResult").Textarea(0))

     

    I'm running my tests using Win8.1 on 2 completely different Virtual Machines. One VM is Parallels on Mac Yosemite and the other Windows Hyper-V. 

     

    I was trying to solve the issue in many different ways but none worked :/. Please help!

     

    The same question on stackoverflow: http://stackoverflow.com/questions/31785691/testcomplete-web-module-keys-method-in-ie11-missing-some-letters

     

     

    • sha's avatar
      sha
      Contributor

      Hi Damians1987,

       

      I had the same problem appr. a year ago. My first solution, which was clumsy, but did the job, was to make a loop that verified the text and reentered it if it was not correct. Finally, I found a way around the problem. As far as I remember, it was adding a Click as you also do.

       

      Sorry for not being able to help you more.

       

      Søren Harder, QA engineer Zmags