At the moment OOBE and login browser tests use a very deep inheritance hierarchy. It is hard to understand what a test is doing and it is hard to modify the base class because so many child tests depend on it in different ways.
Let's eliminate this inheritance and write reusable test components which a specific test injects. Then an OOBE test inherits directly from InProcessBrowserTests and adds the test components it needs. It is then immediately obvious what the test is mocking out and what it needs to run. It is then also easy to write a test that mocks out only xxx component.
Comment 1 by weifangsun@chromium.org
, Dec 7