Need test coverage of --mash |
||||||
Issue descriptionMash browser_tests run in a different environment than chrome --mash does. We need at least one test of this config, or ideally mash browser_tests run in exactly the same was as chrome --mash does.
,
Mar 1 2017
,
Apr 4 2017
,
Aug 30 2017
,
Aug 30 2017
It would be good to either get direct testing of the current chrome --mash startup code. Either via a new test, or by refactoring how mash_browser_tests starts up.
,
Aug 30 2017
I think we'll get this if we move the service_manager into the chrome process as I did for --mus. It's not what we want long term, but at least in the near term (first version of --mash) it's useful and simplifies things.
,
Mar 12 2018
As noted in issue 678687 the service manager is currently in the browser process. So as of now we have this coverage in the tests. We may have to revisit this if the service manager is moved back out in the future. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jamescook@chromium.org
, Jan 13 2017