I am checking for element in the screen not exist, I used "Wait element not exist", the element in the screen was exist, I expect this test should fail, but the check is pass, but when I add Execution Delay "Wait for '500' " before the checking, the test for element not exist is fail as expected. My questions are, how I know I need to add exection delay? and do I used the wright command for checking on element does not exist?
Your help and support is much appreciated
Talal
5 Answers, 1 is accepted
I can confirm you are using the right approach. The only reason I can think of to explain why adding a 500ms delay would make a difference is if the element was being added at the time your wait for element not exist was executing. For example:
Step 14 click a button which causes the UI to change, adding the element that step 15 will check
Step 15 Wait for element exists not
Step 15 may unexpectedly pass because it's easy for the test script to outrun the application you're testing. In this case adding the 500ms delay is the right thing to do.
Cody
the Telerik team
Test Studio Trainings
Rank 1
Regards
Talal
Unfortunately every application is unique. As a result there is no such thing as a standard delay you can use. I'd like to better understand the problem you are running into. Is there any way I can access your application directly so i can see the problem you're running into first hand? Can you give me specific repro steps for me to follow?
All the best,Cody
the Telerik team
Test Studio Trainings
Rank 1
http://www.telerik.com/automated-testing-tools/community/forums/test-studio/general-discussions/waituntilready-is-not-working-as-expected.aspx
Your help would be greatly appreciated
Thanks
I apologize for the delay. I just responded to your own form post on this subject. Let's continue our discussion there.
Greetings,Cody
the Telerik team
Test Studio Trainings