Unable to run Dartium coverage on OS X?

[travissanderson-wf]

I am maybe missing something but it appears that you can't actually run Dartium coverage from OS X. Homebrew-installed dartium is actually just a bash script:

#!/bin/bash
open "/usr/local/Cellar/dartium/1.8.0/Chromium.app" "$@"

so the flag --remote-debugging-port=NNNN is not passed in. Trying to open the executable directly, the flag doesn't seem to have any effect:

$ /usr/local/Cellar/dartium/1.8.0/Chromium.app/Contents/MacOS/Chromium --remote-debugging-port=8050

Is there some other way to run coverage thru Dartium? The majority of this project's tests depend on dart:html so we can't run coverage without running in Dartium.

[travissanderson-wf]

open has an --args option to forward arguments to the executable, but that also doesn't seem to be working.

[zoechi]

What do you expect to happen?
What happens when you run Chromium this way and afterwards run coverage?

[travissanderson-wf]

Chromium doesn't seem to be receiving the --remote-debugging-port=8050 argument and so it doesn't ever connect with the coverage server, so I don't get anything in my output coverage.json.

[zoechi]

Have you tried the other way around - starting Chromium and only afterwards starting coverage?

[travissanderson-wf]

Yes, same result

[travissanderson-wf]

I have no problems running coverage using the command line VM but when I try to launch Dartium and then navigate to my test runner, it doesn't generate coverage. However, if I open a browser tab with localhost:8050 it definitely loads up the remote debugging interface, so I'm not sure what is going wrong here.

[travissanderson-wf]

It turns out due to using IntelliJ there was an extension conflict, so using --disable-extensions resolved the issue for me.