No communication from the web browser has been detected

Jan 24, 2012 at 11:54 AM

Hi

I'm struggling with integrating Statlight Tests for our viewmodels into our TFS Build Process for some time now. I've followed the workflow outlined in this article: http://www.nielshebling.de/?p=167

While I am able to run the Generic Test locally just fine, the test always fails on the build server with the following output:

StatLight - Version 1.6.4372Copyright (C) 2009-2011 Jason JarrettAll Rights Reserved.


Starting Test Run: 24.01.2012 11:24:48

No communication from the web browser has been detected. We've waited longer than the configured time of 00:05:00
------------------ Test Failed ------------------Test Namespace:    Test Class:        Test Method:       Other Info:        No communication from the web browser has been detected. We've waited longer than the configured time of 00:05:00

The sole current test case is an async test which contains just one line EnqueueTestComplete.

Any suggestions?

Coordinator
Jan 25, 2012 at 3:20 AM

Bummer to hear you're having the trouble.

Did you review what is talked about in the documentation? http://statlight.codeplex.com/documentation

If so, and you've tried some of the suggested steps, would you mind including the "--debug" parameter and re-posting so I can take a look in more detail how you are running?

Jan 25, 2012 at 7:03 AM
Edited Jan 25, 2012 at 7:03 AM

Hi

I've added the --debug switch and this is the output I got:

StatLight - Version 1.6.4372

Copyright (C) 2009-2011 Jason Jarrett

All Rights Reserved.

 

****************** Input options as configured ******************

ContinuousIntegrationMode          : False

DllPaths                           : IEnumerable<string>

                                     {

                                     }

ForceBrowserStart                  : False

IsRequestingDebug                  : True

MethodsToTest                      : IEnumerable<string>

                                     {

                                     }

MicrosoftTestingFrameworkVersion   :

NumberOfBrowserHosts               : 1

OutputForTeamCity                  : False

QueryString                        :

ReportOutputFileType               : MSGenericTest

ReportOutputPath                   : C:\B\50\198\TestResults\TFS2010BUILD_XXX-H-TFSBA-01 2012-01-25 08_53_24_Any CPU_Debug\In\4cb97508-48e7-4ead-8b32-bcbe9e137a26\XXX-H-TFSBA-01\DMS.ViewModels.UnitTest.xml

StartWebServerOnly                 : False

TagFilters                         :

UnitTestProviderType               : Undefined

UseRemoteTestPage                  : False

WebBrowserType                     : SelfHosted

WindowGeometry                     : StatLight.Core.Configuration.WindowGeometry

XapPaths                           : IEnumerable<string>

                                     {

                                       'C:\B\50\198\TestResults\TFS2010BUILD_XXX-H-TFSBA-01 2012-01-25 08_53_24_Any CPU_Debug\Out\DMS.ViewModels.UnitTest.xap'

                                     }

*****************************************************************

Starting configuration for: C:\B\50\198\TestResults\TFS2010BUILD_XXX-H-TFSBA-01 2012-01-25 08_53_24_Any CPU_Debug\Out\DMS.ViewModels.UnitTest.xap

XapItems.FilesContainedWithinXap = AppManifest.xaml

XapItems.FilesContainedWithinXap = Castle.Core.dll

XapItems.FilesContainedWithinXap = DMS.ViewModels.UnitTest.dll

XapItems.FilesContainedWithinXap = Microsoft.Silverlight.Testing.dll

XapItems.FilesContainedWithinXap = Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll

XapItems.FilesContainedWithinXap = Moq.Silverlight.dll

Incoming Microsoft.Silverlight.Testing.dll file's hash = 357A677957F309AE85C3E5AEEDA43A32BCA23AD3

RunnerType = OneTimeConsole

Attempting to open port at http://localhost:8887/

testPageUrlWithQueryString = http://localhost:8887/GetHtmlTestPage?

IRunner typeof(OnetimeRunner)

 

 

Starting Test Run: 25.01.2012 08:53:25

 

Listening on http://localhost:8887/

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

COULD NOT FIND THE AUTOMATION ELEMENT FOR processId 8100

 

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

 

------------------ Test Failed ------------------

Test Namespace:   

Test Class:       

Test Method:      

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

-------------------------------------------------

webBrowser.Stop()

********************************************

Error Summary for: C:\B\50\198\TestResults\TFS2010BUILD_XXX-H-TFSBA-01 2012-01-25 08_53_24_Any CPU_Debug\Out\DMS.ViewModels.UnitTest.xap

 

------------------ Test Failed ------------------

Test Namespace:   

Test Class:       

Test Method:      

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

-------------------------------------------------

********************************************

 

*************** Summary ********************

********************************************

Total          : 1

Successful     : 0

Failed         : 1

Ignored        : 0

Completion End : 25.01.2012 08:58:26

Duration       : 00:05:01.1234197

********************************************

*********************************

Wrote XML report to:

C:\B\50\198\TestResults\TFS2010BUILD_XXX-H-TFSBA-01 2012-01-25 08_53_24_Any CPU_Debug\In\4cb97508-48e7-4ead-8b32-bcbe9e137a26\XXX-H-TFSBA-01\DMS.ViewModels.UnitTest.xml

*********************************


Coordinator
Jan 26, 2012 at 3:23 AM

Ok, I see you're using the StatLight - Version 1.6.4372, and are leveraging the MSTest build from April 2010. 

Is your project a SL5 or SL4 project?

If it is SL5, do you have SL5 installed on the server as well?

If it is SL4, you may need to consider using StatLight 1.5 to run your tests. Give that a try and let me know how it goes.

(Sorry my responses are a little slow, on a travel business trip ATM)

 

Jan 26, 2012 at 6:27 AM

Hi

The project is indeed a SL5 project and the Silverlight 5 Runtime is installed on the server as well.

Cheers

Apr 27, 2012 at 7:59 AM

Hi,

Unfortunatelly, I have the exactly same error as erazor for the same configuration(SL5 on TFS), it works just fine locally.

did anyone solve this issue?

Thanks

Coordinator
Apr 27, 2012 at 6:20 PM

What if you RDP in to the TFS server and try to run statlight manually? Do you notice anything different there?

May 3, 2012 at 7:57 AM

Thanks for your answer.

I've run the tests manually and there is no difference. Then I've checked the build server configuration/installations and noticed that the Silverlight 5 Runtime was missing :D(only SDK was installed). After installing the Runtime, the test were running.

 

Coordinator
May 3, 2012 at 3:33 PM

Thanks for letting me know what the issue was. 

Happy Testing!