A specific customer test, when run in Chrome, is frequently (but randomly) failing while running. The customer is using https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg to simulate that the browsers are on a mobile device. So, this causes the website to behave differently (it thinks it's talking to an iPhone). The test log shows: '8/20/2014 2:01:52 PM' - 'Fail' : 37. Verify 'InnerText' 'Contains' 'Lingerie' on 'CategoryHeading' ------------------------------------------------------------ Failure Information: ~~~~~~~~~~~~~~~ ExecuteCommand failed! BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'8233b98f-2478-4409-8d22-c5b011da8938',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'') InnerException: System.TimeoutException: Timed out waiting for command to be handled at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout) at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId) at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request) InnerException: ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed! BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'8233b98f-2478-4409-8d22-c5b011da8938',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'') InnerException: System.TimeoutException: Timed out waiting for command to be handled at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout) at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId) at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request) ---> System.TimeoutException: Timed out waiting for command to be handled at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout) at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId) at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request) --- End of inner exception stack trace --- at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request) at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady) at ArtOfTest.WebAii.Core.Browser.RefreshDomTree() at ArtOfTest.WebAii.Core.Browser.ArtOfTest.Common.IAutomationHost.EnsureStateIsCurrent() at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.WaitForAllElements(IAutomationHost host, AutomationDescriptor descriptor, Int32 timeout) at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteStep(Int32 order) Most of the time it fails on one of the many Verify steps, but you cannot predict which one. I tried increasing the WebKitExecutionDelay to solve the problem. It did not help. The test that demonstrates the problem will be attached to the internal bug report.