On: Headless Chrome is coming soon

[juliangamble]

Another way to solve this problem is to have Chrome in a docker container that you can start up: https://github.com/SeleniumHQ/docker-selenium

[killing_time → juliangamble]

I use the Chrome and Firefox docker-selenium containers in Testcontainers [1][2], my project for running containers to support JUnit tests.

I created this after numerous issues with PhantomJS compatibility and debuggability; Testcontainers instead uses the real browsers, and also offers automatic video recording of test sessions and VNC access for debugging.

Headless chrome support sounds like a good step forward, but if visibility into what's going on is limited then I feel there's going to be some way to go. Perhaps chrome remote debugging support?

[1]: http://testcontainers.viewdocs.io/testcontainers-java/ [2]: https://rnorth.org/26/better-junit-selenium-testing-with-doc...

[elgalu → killing_time]

Thanks for noticing, I upgraded the "Alternatives" section at https://github.com/elgalu/docker-selenium#alternatives

[duaneb → killing_time]

Just because it is headless doesn't mean it can't render to a serializable format (like a pdf)