1
Vote

No communication from the web browser has been detected. We've waited longer than the configured time of 00:05:00

description

Hi,
We run several Silverlight tests using statlight.exe as part of our build.
We found this error happen randomly not in particular test or test assembly.
The statlight browser stays in the loading screen until it timeout. attached is the test output file showing the problem

Thanks,

exec] ------------------ Test Failed ------------------
 [exec] Test Namespace:    
 [exec] Test Class:        
 [exec] Test Method:       
 [exec] Other Info:        No communication from the web browser has been detected. We've waited longer than the configured time of 00:05:00
 [exec] -------------------------------------------------
 [exec] webBrowser.Stop()
 [exec] ********************************************
 [exec] Error Summary for: C:\.Silverlight.Tests.xap
 [exec] 
 [exec] ------------------ Test Failed ------------------
 [exec] Test Namespace:    
 [exec] Test Class:        
 [exec] Test Method:       
 [exec] Other Info:        No communication from the web browser has been detected. We've waited longer than the configured time of 00:05:00
 [exec] -------------------------------------------------

file attachments

comments

panny wrote Jul 26, 2013 at 4:06 AM

I'm having a similar issue.

I'm trying to launch multiple instances of statlight with continuous attached such that I can observe multiple xap files being tested in parallel.

My guess is that this does not work as the browser behind the scene has been shut down and they share a common static instance.

For now, I've settled with a single threaded application that runs X amount of xap files, and collect up the xml files as an output and feed all the xml files to me.

I hope this helps. I would like to see support for multiple instances of statlight observing multiple xap files.

panny wrote Jul 31, 2013 at 12:08 AM

Since my last post, i've looked at File System Watcher and put that into a queue to run statlight tests one after the other. Redirect the statlight output to a console window and off you go.

Deciding on what files you will be observing with the watcher is up to you. Hope this helps.