Forum Discussion

JennyH11's avatar
JennyH11
Frequent Contributor
7 years ago

HScroll not working in KWTest

Hi Everyone!   I'm struggling to get a Horizontal Scroll to to set position using the HScroll object in a keyword test. All the others work in the test except one. The only difference is the posi...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    When you say "doesn't work", are there errors in your log or any other messages that indicate what might be going on?

     

    You seem to have gone through all the basic trial/error stuff I would have suggested.  One thing to think about... is the HScroll on screen when you run the test full speed?  I've seen somethings happen, sometimes, where if a component is not on screen, while it may LOOK like everything is working, it doesn't really work right because you can't interact with it.  

     

    Since this is a desktop application, see if there's some sort of VScroll or Page Down that you might be able to do to get the component on screen before you attempt to work with it.

tristaanogre's avatar
tristaanogre
Esteemed Contributor

When you say "doesn't work", are there errors in your log or any other messages that indicate what might be going on?

 

You seem to have gone through all the basic trial/error stuff I would have suggested.  One thing to think about... is the HScroll on screen when you run the test full speed?  I've seen somethings happen, sometimes, where if a component is not on screen, while it may LOOK like everything is working, it doesn't really work right because you can't interact with it.  

 

Since this is a desktop application, see if there's some sort of VScroll or Page Down that you might be able to do to get the component on screen before you attempt to work with it.

Marsha_R's avatar
Marsha_R
Moderator
7 years ago

Try putting a breakpoint in somewhere above the scroll so the test stops and then step through the test a line at a time.  Sometimes you can see things happen this way that aren't obvious when the test runs on its own.

  • JennyH11's avatar
    JennyH11
    Frequent Contributor
    7 years ago

    Thanks Marsha!

     

    I need a bit more practise with using breakpoints, stepping through, over etc... Up until now I've only used Stop executions as I feel like I've got more control over the test. I also found that with the mouse disabled during test runs, if I pause or the test pauses because on a breakpoint, I cannot use the mouse. Therefore, I've continued to use Stops and not breakpoints as I don't want to have the mouse enabled when tests run.

     

    I presume this is how it is designed and most users do not disable the mouse and therefore do not see this issue?

    • Marsha_R's avatar
      Marsha_R
      Moderator
      7 years ago

      The breakpoints and other debug features are very useful.  Stopping the test loses the state of everything and you can't see what happened.  If you pause at a breakpoint and then proceed through the code, you may find that the test is not doing exactly what you intended.  Watching it at regular speed can hide this.  

       

      I've never had occasion to disable the mouse.  Usually the tests are running on a machine on my desk or on a vm and nothing interferes.  If I need to test on a public machine somewhere, then I just make a quick sign to please don't disturb this and lay it over the keyboard and mouse.