Verify Exists steps fails immediately without waiting through timeout

Hello Ory,

You can easily change the role of that step. You can do that by right-clicking on the step>Change Role>Set As Wait(see screenshot). Test Studio will wait for that condition to be true (up to the time set) until proceeding with the test (instead of checking once and failing if false). See this article for more information.

Regards,
Plamen
the Telerik team

Hi Plamen,

I am not sure you understood the problem... I have no need to change the role of any steps.

The problem described is that it does not "wait for that condition to be true (up to the time set)" as you say it should. It fails immediately without waiting the set amount of time. Please re-read my post and see the screenshot.

Thanks,
Ory

Hello Ory,

I think I understand exactly what the problem is. You are using a "Verify Exists" step inside of the If/else statement and your test fails on that step, because the element cannot be found. The problem is that the "Verify Exists" step performs the verification only once against the cached copy of the DOM tree(it doesn't wait for the element to exists). 
 
One way to overcome this is to add a fixed execution delay step right before the "Verify Exists" step, but we don't recommend this approach.

Another option is to set the EnsureStateIsCurrent property on that step to True(see screenshot). This will refresh the DOM tree before performing the verification, but this still does not guarantee that the verification will succeed.
 
The best approach in this case is described in this article from our Troubleshooting Guide. If you change the verification from "Verify Exists" to "Wait For Exists", Test Studio will wait up to the time set in the Timeout property(see screenshot), refreshing the DOM tree on every 500 ms, and when the element is found will proceed with the next step.

Regards,
Plamen
the Telerik team

Hi Plamen,

Sorry for the long reply time, have been busy with other things.

I have done as you suggested and it has solved the problem perfectly.

Thanks,
Ory

Hello Ory,

Glad to hear it! Thanks for the update.

Kind regards,
Plamen
the Telerik team

What would be best practice to do this opposite of this?  I want to verify that an element DOES NOT exist depending on a condition.

Example:
A notification button, depending on a DB flag, will show a badge.  I query the DB for the flag value, and based on it's value will either verify that the badge is visible (if flag = true) or that the badge is not present.  I cannot use the .visible option because the element does not exist if the DB = false.  I figured that I could check to make sure the element does not exist if the DB flag = false instead of visible.  What would be the best way to handle this in a coded step?

Thanks!!

Hello Gregory,

This is a duplicate of ticket number 796285, let's continue the discussion there.

Regards,
Boyan Boev
Telerik