WaitforExists not continue when found

2 posts, 0 answers
  1. Tim
    Tim avatar
    4 posts
    Member since:
    Nov 2019

    Posted 22 Nov 2019 Link to this post

    Due to having to await a 2nd URL to load, I am being forced to add a 60 second WaitforExists against an element.  The variable against the step are;

    CheckInterval; 500

    Exists; ticked

    IsWaitOnly; ticked

    Pause; None

    StepTyoe; Wait

    SupportsWait; ticked

    Timeout; 60000

    However, although there is a CheckInterval, the 'continue' for the task is not kicking in until after the full 60 seconds has elapsed.

    Is there something I am missing, or should I try a different 'wait' command?

  2. Plamen Mitrev
    Plamen Mitrev avatar
    214 posts

    Posted 22 Nov 2019 Link to this post

    Hi Tim,

    It seems to me that the configuration you currently have should be working as expected. I recorded a sample test against https://www.bing.com and basically searched for something and used a WaitForExists step with the default (same properties as yours). Once the page was fully loaded, the test runner found the element in the DOM tree and the step passed. This leads me to believe that this behavior might be specific to the application under test and if the page is fully loaded in the Timeout time.

    I would like to investigate the issue further and assist you. To do that, I need you help to gain access to the application under test. Please also share a sample Test Studio project, that simulates the issue. I will analyze it and debug it on my end.

    In the meantime, you can try that step and properties against a publicly accessible application, like I did. Please let me know what is the behavior in that case.

    Thank you for your cooperation in advance.

    Plamen Mitrev
    Progress Telerik

    The New Release of Telerik Test Studio Is Here! Download, install,
    and send us your feedback!
Back to Top