Hi,
I am using Visual Studio plugin of Telerik test studio (Mbunit cases) to automate my web application. On my site there is a link which takes around 120 seconds to navigate to next page.
The issue I am facing is that the during playback the link gets clicked but the following execption is generated before navigation to next page where i want to verify assertions.
System.TimeoutException : Wait for condition has timed out
at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo)
at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait)
at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
at ArtOfTest.WebAii.Core.Browser.WaitUntilReady()
at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request)
at ArtOfTest.WebAii.Core.Actions.Click(Element targetElement)
at ArtOfTest.WebAii.Controls.HtmlControls.HtmlControl.Click()
How can i handle this, i have even increaed the WaitOnElement timeout to 180000, but thats of no use.
I am using Visual Studio plugin of Telerik test studio (Mbunit cases) to automate my web application. On my site there is a link which takes around 120 seconds to navigate to next page.
The issue I am facing is that the during playback the link gets clicked but the following execption is generated before navigation to next page where i want to verify assertions.
System
How can i handle this, i have even increaed the WaitOnElement timeout to 180000, but thats of no use.
1 Answer, 1 is accepted
0
Hi Rohit,
if it's the navigation that takes 120 seconds then you'll need to increase the timeout for the step AFTER the click.
Also, you should consider that Waiting for an element in code is a bit tricky as seen here:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/code-samples/general/wait-for-element-to-exist-in-code.aspx
You probably need to implement such a wait for the element the test is trying to locate after it has performed the click.
Also, it's possible that the problem is different altogether, it's hard to say without additional info on this. If the above solution does not workout, please provide additional info as seen here:
http://tv.telerik.com/watch/automated-testing-tools/test-studio-submitting-support-ticket-for-playback-issues
Best wishes,
Stoich
the Telerik team
if it's the navigation that takes 120 seconds then you'll need to increase the timeout for the step AFTER the click.
Also, you should consider that Waiting for an element in code is a bit tricky as seen here:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/code-samples/general/wait-for-element-to-exist-in-code.aspx
You probably need to implement such a wait for the element the test is trying to locate after it has performed the click.
Also, it's possible that the problem is different altogether, it's hard to say without additional info on this. If the above solution does not workout, please provide additional info as seen here:
http://tv.telerik.com/watch/automated-testing-tools/test-studio-submitting-support-ticket-for-playback-issues
Best wishes,
Stoich
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items