Forum Discussion

DIMWSH's avatar
DIMWSH
New Contributor
7 years ago

Testobject.Click doesnt always work

I'm testing a web application and I have a few actions on test objects that involve clicking a button or a link to navigate to a different page, or to click a radio button on a page. All of these tes...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    Without knowing more detail about the specifics of the objects, my best guess is that the "Click" action is being performed just fine but the object being clicked may not be ready to be clicked... It's present on screen but not enabled, or there's a background process that needs to finish, or something like that.  It has all the earmarks of a "timing" problem where the automation is running faster than the application can perform.  I'd start with adding logic to check the component in question to determine if it is ready to be clicked before executing the click.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

Without knowing more detail about the specifics of the objects, my best guess is that the "Click" action is being performed just fine but the object being clicked may not be ready to be clicked... It's present on screen but not enabled, or there's a background process that needs to finish, or something like that.  It has all the earmarks of a "timing" problem where the automation is running faster than the application can perform.  I'd start with adding logic to check the component in question to determine if it is ready to be clicked before executing the click.

  • DIMWSH's avatar
    DIMWSH
    New Contributor
    7 years ago

     I'll give that a shot! Thanks

    • AlexKaras's avatar
      AlexKaras
      Champion Level 3
      7 years ago

      Hi,

       

      Yes, I am completely with Robert - .Click() must work, otherwise this forum had to explode from complaints about not working tests. :) But, alas!, the nature of most modern web applications is that there are too many background actions done via scripting on the page and the page well may not respond until all those actions are done. If this is the case, you should find indicators that signal that the page and the given control are ready to interact with end-user and delay your screen actions (clicks, keys typing, drags, etc.) until the page and control are ready.