We have a RuleBasedHostResolverProc in the browser test harness which tests use to setup rules like map google.com->localhost. This works by modifying globals in net/ for host resolving, but doesn't work when network code is running in a different process.
This bug tracks having the browser test harness automatically send these rules to the network process when it's in use.
In doing this work, I'll have to refactor some code in the browser test harnesses to make the base browser test harness be able to inject code in between SetUpOnMainThread and running the test. We would then enforce that changes to the host resolver have to be done only in SetUpOnMainThread. Most tests do this already, but not all.
While doing the above refactoring, I noticed we don't need SetUpInProcessBrowserTestFixture anymore since we have SetUpOnMainThread now. It was added in https://src.chromium.org/viewvc/chrome?view=revision&revision=26938 but I confirmed we don't need it anymore.
Comment 1 by bugdroid1@chromium.org
, Apr 20 2017