Hi,
I am using Test Studio to record scripts on a web application. There are some elements that get displayed only after a background script is executed based on a previous selection. The background script execution varies in time and so i have tried enabling the usestepwaitonelements which for some reason does not work always (it seems to work sometimes) and also I tried using an execution delay which works. We do not want to use the execution delay unless necessary as the script execution gets delayed even when not necessary.
What options do i have to set to make the usestepwaitonelements to work on my scripts.
Thanks
I am using Test Studio to record scripts on a web application. There are some elements that get displayed only after a background script is executed based on a previous selection. The background script execution varies in time and so i have tried enabling the usestepwaitonelements which for some reason does not work always (it seems to work sometimes) and also I tried using an execution delay which works. We do not want to use the execution delay unless necessary as the script execution gets delayed even when not necessary.
What options do i have to set to make the usestepwaitonelements to work on my scripts.
Thanks
1 Answer, 1 is accepted
0
Hi Brian,
When you set the 'UseStepWaitOnElementsTimeout' property to True, did you increase the default value of the 'WaitOnElementsTimeout"? Please see this article explaining the connection between these two properties.
You can also add a "Wait for exists" step right before the failing step. See this article on how to do that.
If you continue to have difficulty, please provide the exported step failure details for analysis. A Jing video demonstrating the issue may also help us to better understand what is happening.
All the best,
Plamen
the Telerik team
When you set the 'UseStepWaitOnElementsTimeout' property to True, did you increase the default value of the 'WaitOnElementsTimeout"? Please see this article explaining the connection between these two properties.
You can also add a "Wait for exists" step right before the failing step. See this article on how to do that.
If you continue to have difficulty, please provide the exported step failure details for analysis. A Jing video demonstrating the issue may also help us to better understand what is happening.
All the best,
Plamen
the Telerik team
Are you enjoying Test Studio? We’d appreciate your vote in the ATI automation awards.
Vote now
Vote now