#317 switch to ChromeHeadless #318
Conversation
|
Looks like the build failed because chrome was not version 64 or above. I can't tell what version is installed. If you can determine what version is installed, you can find the right chromedriver version here: https://sites.google.com/a/chromium.org/chromedriver/downloads Then you can adjust the version of the nuget package to correspond: |
|
/cc @cgravill any ideas how to configure it on appveyor and travis? |
|
I have AppVeyor working on #319 by downgrading the the driver slightly (Selenium.WebDriver.ChromeDriver = 2.36). Using the TravisCI Chrome add-in it's attempting to run on TravisCI, however, it looks like it might be an old version of Chrome on there. We might be able to update Chrome that machine to something recent. |
|
@forki I got the tests working on Travis on #319 as well by doing a full install of Chrome. What I did may be a bit outdated compared to https://docs.travis-ci.com/user/gui-and-headless-browsers/ but equally TravisCI's bundled versions of Chrome are now so old as to be problematic. Thoughts? |
|
can we somehow ask the travis guys to update? |
|
They seem pretty slow at upgrading - latest image is 14.04! I tieded up the approach here so it no longer fakes a display with xvfb and definitely runs fully headless. It’s also using the same approach used to install Yarn. Rather than rely on TravisCI updating this seems like a decent approach. |
|
that's done now |
I did the best I could testing this. I could only run via command line, I couldn't get the right combo of stuff installed so that VS would open the project.
Using regular chrome it works and is VERY slow (I stopped it not knowing how many tests there were). I then switched to ChromeHeadless and it also worked (slowly) but the last test failed.
Concerned about the speed I went to localhost:8085 and there was a noticeable lag as I typed into the box, so I don't think the slowness is related to the changes I made.