Hello,
I am running my Automation scripts through Jenkins for CI. When the environment finishes building, then my tests get ran. The first test after a fresh build always throws this requested resource is in use for IE. I have attached the result from Jenkins. Is there a setting i'm missing that will fix this from not happening? Is there a command that I need to put in my navigate test?
7 Answers, 1 is accepted
It is very interesting as well as intriguing. I noticed the failure is happening on immediately after a Clear Cookies step. This gives me an idea, a possible theory as to what's going on.
Step 1: Clear Cookies - the browser STARTS clearing the cookies left over from the previous set of tests. In theory this step is not supposed to continue until the browser is 100% complete with clearing cookies. But what if it's continuing prematurely?
Step 2: The Navigate step - the browser hasn't yet finished clearing cookies and as a result returns "The requested resource is in use."
Right now this is just a hypothesis on my part. To prove or disprove this theory try adding a fixed Execution Delay of about 5 seconds in between those two steps. If this solves the problem I'll file a problem report in our system about this.
Let me know the results.
Regards,
Boyan Boev
Telerik
Hi Boyan,
After looking at it on my end, I'm pretty sure that it is the delay right after the environment is deployed. Because in Jenkins once an environment is deployed, it takes a few moments to initialize, and my tests are being ran right after the deploy is finished. So I think thats where my problem is at. The Execution Delay might work for that. And instead of putting it in my Navigate step (as I call that Navigate step on multiple tests on my test list, and that add too much time for my tests) I am going to just add an Execution test and then add it at the beginning of my Test List. I will add this and let you know how it goes.
That makes sense.
Please take your time and update this ticket accordingly.
Regards,
Boyan Boev
Telerik
Boyan, I fixed the IE resource in use by adding a wait, but now when a build has finished in Jenkins, and my Test is kicked off and ran, i get the 'Wait for condition has timed out' message.
Attached is my Test and the Results from Jenkins ran.
Would you know of what this error is:
Wait for condition has timed out
InnerException:
System.TimeoutException: Wait for condition has timed out
at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
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.Browser.InternalNavigateTo(Uri uri, Boolean useDecodedUrl)
at ArtOfTest.WebAii.Core.Browser.NavigateTo(Uri uri, Boolean useDecodedUrl)
at ArtOfTest.WebAii.Core.Browser.NavigateTo(String url, Boolean useDecodedUrl)
at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.NavigateToActionDescriptor.Execute(Browser browser)
at ArtOfTest.WebAii.Design.Extensibility.HtmlActionDescriptor.Execute(IAutomationHost autoHost)
at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteStep(Int32 order)
I can see that you don't use Clear Browse Cache step anymore. Why do you have delay step in that case? Also you don't need to create a separate test just for a single delay step.
You can put it as single step in the main test.
Regarding the issue, do you get the same problem when you execute the test list directly from Test Studio and not via Jenkins?
Have you calibrated your browser?
Hope to hear from you soon.
Regards,
Boyan Boev
Telerik
I am glad you have found a resolution.
If you have any additional questions please do not hesitate to contact us again.
Regards,
Boyan Boev
Telerik