tag:help.appveyor.com,2012-11-13:/discussions/problems/570-selenium-testsAppVeyor: Discussion 2018-08-25T01:50:18Ztag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T15:58:08Z2014-07-21T15:58:08ZSelenium Tests<div><p>I've tried to disable that logging for FireFox at no avail. I
suspect those messages come directly from FireFox to StdOut. Though
Chrome driver seems working the best.</p>
<p>Regarding "they're being flagged in red in the console" - could
you please drop a screenshot of console to see how it looks
like?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T16:02:23Z2014-07-21T16:02:23ZSelenium Tests<div><p>Is this OK</p></div>scascarinitag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T16:04:18Z2014-07-21T16:04:18ZSelenium Tests<div><p>Not sure if that's too big - how about</p>
<p><a href=
"https://www.dropbox.com/s/flidvm5u78lr7pc/Screenshot%202014-07-21%2017.00.55.png">
https://www.dropbox.com/s/flidvm5u78lr7pc/Screenshot%202014-07-21%2...</a></p></div>scascarinitag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T16:05:51Z2014-07-21T16:05:51ZSelenium Tests<div><p>I see. Do you call <code>vstest.console</code> command as part
of your build script, not using tests "autodiscovery"?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T16:07:47Z2014-07-21T16:07:47ZSelenium Tests<div><p>Yes because I want to run the tests after deployment.</p></div>scascarinitag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T16:12:37Z2014-07-21T16:12:37ZSelenium Tests<div><p>Perfect! The problem is that PowerShell treats everything
written to StdErr as exceptions. Switch "after deploy" script to
"CMD" mode - that should fix a problem.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/338486202014-07-21T16:49:39Z2014-07-21T16:49:39ZSelenium Tests<div><p>OK tweaked that and kicked off a new build. All looking good so
far - tests are running and console is clear.</p>
<p>Thanks again.</p></div>scascarinitag:help.appveyor.com,2012-11-13:Comment/338486202014-07-22T10:35:24Z2014-07-22T10:35:24ZSelenium Tests<div><p>So the tests run as 'CMD' but run very slowly. About 5 ran in 30
minutes and then the build timed out.</p>
<p>Based on your comments above I did some experimenting and found
that if I set the <code>/InIsolation</code> flag I could switch
back to running under Powershell and I don't see any errors in the
console.</p>
<p>So I'm happy but you may want to investigate why the tests ran
so slowly under 'cmd'. I was running</p>
<p><code>vstest.console /logger:Appveyor
test/bin/Debug/Spiro.Angular.Selenium.Test.dll</code></p>
<p>as an after deployment script and it ran 5 selenium tests in 30
minutes</p>
<p>Currently I'm running</p>
<p><code>vstest.console /logger:Appveyor /InIsolation
test/bin/Debug/Spiro.Angular.Selenium.Test.dll</code></p>
<p>as Powershell and it runs about 50 selenium tests in 15 minutes
or so.</p>
<p>Thanks for all your help.</p></div>scascarinitag:help.appveyor.com,2012-11-13:Comment/338486202014-07-22T14:10:00Z2014-07-22T14:10:00ZSelenium Tests<div><p>Wow, that's really interesting observation! I will try to
understand this difference between PS and external command
mode.</p>
<p>Thank you for the update!</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/338486202014-11-27T12:05:14Z2014-12-25T07:50:25ZSelenium Tests<div><p>Hello guys,</p>
<p>Any updates on the issue? Why there is a time difference ?</p>
<p>We are also suffering from slow acceptance tests.</p></div>Rifat Erdem Sahintag:help.appveyor.com,2012-11-13:Comment/338486202014-11-27T19:02:00Z2015-04-03T15:33:57ZSelenium Tests<div><p>I believe it's been fixed for the new environment.</p>
<p>Look at that: <a href="https://ci.appveyor.com/project/FeodorFitsner/selenium-tests/build/1.0.10">
https://ci.appveyor.com/project/FeodorFitsner/selenium-tests/build/...</a>
- ran basic Selenium test against FF, Chrome and IE (!) drivers in
just 47 seconds. Artifacts contain screenshots.</p></div>Feodor Fitsner