Unittests should not need to instantiate a full ChromeBrowserProviderImpl in order to pass without crashing.
For some tests, we will be able to install a fake provider that feeds dummy data into the test.
For other tests, we may need to instantiate a real sub-provider. These tests should be rare, however, and they should only require a specific sub-provider, not a full ChromeBrowserProviderImpl.
Once this is done, the only include of chrome_browser_provider_impl.h is from the file that installs it at startup.
Unittests should not need to instantiate a full ChromeBrowserProviderImpl in order to pass without crashing.
For some tests, we will be able to install a fake provider that feeds dummy data into the test.
For other tests, we may need to instantiate a real sub-provider. These tests should be rare, however, and they should only require a specific sub-provider, not a full ChromeBrowserProviderImpl.
Once this is done, the only include of chrome_browser_provider_impl.h will be from the file that installs it at startup.
Comment 1 by rohitrao@chromium.org
, Nov 15 2016