What can I do if the browser crashes

Hello Wade,

Do you have any clues or insight as to when/why IE is crashing? The best solution of course is to get to the bottom of this and stop the crashes from happening in the first place.

The only possible work around is to enable KillBrowserProcessOnClose in the test list settings. That might help control the damage caused by an IE crash and help the test list recover from it.


Regards,
Cody
Telerik

Here is where the step failed. BTW this is IE 8

ArtOfTest.Common.Design.Exceptions.ExecutionException: ExecuteCommand failed!
InError set by the client. Client Error:
System.ArgumentException: Tag collection of 'a' elements is either empty or has less elements than the element occurrence requested. RequestedIndex: '316', ElementLength: '0'
   at ArtOfTest.InternetExplorer.IECommandProcessor.FindElement(ElementIdMessage id)
   at ArtOfTest.InternetExplorer.IECommandProcessor.ProcessActionCommands(BrowserCommand request)
   at ArtOfTest.InternetExplorer.IECommandProcessor.ProcessCommand(WebBrowserClass ieInstance, BrowserCommand request, IHTMLDocument2 document)
BrowserCommand (Type:'Action',Info:'NotSet',Action:'ScrollToVisible',Target:'ElementId (tagName: 'a',occurrenceIndex: '316')',Data:'1',ClientId:'Client_b73bbf15-9fbd-40af-802a-eda85948f641',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'System.ArgumentException: Tag collection of 'a' elements is either empty or has less elements than the element occurrence requested. RequestedIndex: '316', ElementLength: '0'
   at ArtOfTest.InternetExplorer.IECommandProcessor.FindElement(ElementIdMessage id)
   at ArtOfTest.InternetExplorer.IECommandProcessor.ProcessActionCommands(BrowserCommand request)
   at ArtOfTest.InternetExplorer.IECommandProcessor.ProcessCommand(WebBrowserClass ieInstance, BrowserCommand request, IHTMLDocument2 document)')
InnerException: none.

Hi Wade,

What the error is trying to tell us is that Test Studio was looking for an <a> element (i.e. a hyperlink aka "anchor") but the entire browsers DOM was empty when it went to look for this element. This is usually a very transitory state. Can you share with me what was the test step in this case? Does the test frequently fail at this step? If so there are two possible approaches to overcome this problem:

1) Insert a fixed delay long enough to wait for the DOM to be repopulated by the web application
2) Add a Wait For Exists for the target element right before this problem step


Regards,
Cody
Telerik