WaitOnElementsTimeOutProperty does not function properly

4 posts, 0 answers
  1. Snehal
    Snehal avatar
    1 posts
    Member since:
    Mar 2011

    Posted 17 Mar 2011 Link to this post

    If i set WaitOnElementsTimeOutProperty to increase the wait time and play the recorded test it does not consider the set time and fails that step
  2. Stoich
    Stoich avatar
    1 posts

    Posted 19 Mar 2011 Link to this post

    Hi Snehal,
       I'd like to reproduce this issue. Please record a test against a publicly accessible URL (e.g. Google). Make sure the test exhibits this behavior. Then send me the test along along with info about the failing step.

    I will try to analyze the issue

    Hope to hear from you soon!

    the Telerik team
  3. Pravallika
    Pravallika avatar
    14 posts
    Member since:
    Dec 2014

    Posted 04 Feb 2015 Link to this post

    I'm also facing the same issue. Attached are the two images for the test and coded steps.
    When i record and set the time more than 30 seconds and convert the test step into code, the value is set to 30000 by default.
    Even if I change the time in coded step, telerik recorder doesnot seem to wait for the expected time interval during runtime..

    Please suggest an alternative for explicit wait.
  4. Boyan Boev
    Boyan Boev avatar
    1072 posts

    Posted 09 Feb 2015 Link to this post

    Hi Pravallika,

    This is done by design. When using an UI step it works like expected, however when using code for example:


    It will not reach the WaitForExist/Visible method at all, ti will fail at the BingDiv part with element not found. Since it fails with element not found in this case the global Wait On Elements will apply not the Wait.ForExists();

    Refer to the screenshot attached.

    In order to achieve this you should find the element in code and wait for it.

    Hope this helps.

    Boyan Boev
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
Back to Top