osx java8 about doo-chrome-devprotocol HOT 1 OPEN

Hi Alex,

It delegates all the launching of Chrome etc to cdp4j so I think yes you'll need those fixes upstream. It works on Java 10 on Linux and Java 8 on Windows (using the WindowsProcessManager) though!

Running these in CI looks like the project's tests, actually, i.e. https://github.com/oliyh/doo-chrome-devprotocol/blob/master/test/doo_chrome_devprotocol/core_test.clj#L7-L8

This, coupled with hooking into the cljs.test/report multimethod to print out teamcity messages, means the CI build passes and fails and reports each test as well.

It's not necessarily any more advanced than doo itself (in many ways it is just a crude wrapper) so I imagine that it's no better placed for proper IDE integration than any other test runner - the main/only advantage over using doo directly is that you don't need npm/karma to run the tests in Chrome!

from doo-chrome-devprotocol.