Mojo utility client should have a fault injection API |
||||
Issue descriptionFor test fixtures in an in-process browser tests, we should be able to cause the mojo utility client host to error (viz., the mojo connection breaks) during a test. Why? So the mojo error callback handling path of mojo client utility host user can be tested from automated test fixtures.
,
Jan 23 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/862ae960ab1fdb4503cd99398f7211473f1134f3 commit 862ae960ab1fdb4503cd99398f7211473f1134f3 Author: noel <noel@chromium.org> Date: Mon Jan 23 16:23:54 2017 UtilityProcessMojoClientBrowserTest: add enum for run options Add process run options as an enum for SANDBOXED, UNSANDBOXED, and ELEVATED, rather than using booleans. BUG= 682549 Review-Url: https://codereview.chromium.org/2645683006 Cr-Commit-Position: refs/heads/master@{#445385} [modify] https://crrev.com/862ae960ab1fdb4503cd99398f7211473f1134f3/content/browser/utility_process_mojo_client_browsertest.cc
,
Jul 17 2017
,
Jul 17 2017
,
Feb 13 2018
This class is going to be removed along with the last direct use of utility processes outside of ServiceManagerContext.
,
Feb 13 2018
Seems good, /mental note utility processes is all servicified these days. |
||||
►
Sign in to add a comment |
||||
Comment 1 by noel@chromium.org
, Jan 19 2017