Hacker News new | comments | show | ask | jobs | submit login

Clarity moved to chrome webdriver, but they are not using the headless features. It's standard selenium webdriver, and xvfb

https://github.com/vmware/clarity/blob/master/.travis.yml#L4...




hi @arwineap, you are right in saying that Clarity is using chrome webdriver + xvfb. That's for the css regression testing, which we haven't looked into moving to use headless Chrome. We've switched our unit tests to use the headless Chrome: https://github.com/vmware/clarity/blob/master/build/karma.co...


Hrm, but those also run in travis right? I noticed at the bottom of the karma.conf it checks to see if it's in travis.

The travis image is installing chrome stable, which is not 59; AFAIK the headless feature is only available in beta right now which versions out to 59.

I admit I'm not sure if your unit tests are running in travis, but if they are, I'd wonder if the --headless flag is just getting dropped as an unknown flag.

Curious either way actually so let me know; I'm looking at starting the testing moving from phantomjs to headless which is why I was sleuthing out Clarity's move


> AFAIK the headless feature is only available in beta right now which versions out to 59.

Headless is pretty stable on Linux in 58. 59 is really when headless became usable on Mac. Still in beta on Windows.




Applications are open for YC Winter 2018

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: