Expose API to store and load data usage stats from UI task runner.

chrome/browser/renderer_context_menu/render_view_context_menu_unittest.cc

Index: chrome/browser/renderer_context_menu/render_view_context_menu_unittest.cc
diff --git a/chrome/browser/renderer_context_menu/render_view_context_menu_unittest.cc b/chrome/browser/renderer_context_menu/render_view_context_menu_unittest.cc
index b3a2c10daea0d509d65820af5aaefed65ec43e95..a08af4006404c73bb350a86d986c2d3f7e923994 100644
--- a/chrome/browser/renderer_context_menu/render_view_context_menu_unittest.cc
+++ b/chrome/browser/renderer_context_menu/render_view_context_menu_unittest.cc
@@ -23,6 +23,7 @@
 #include "chrome/test/base/chrome_render_view_host_test_harness.h"
 #include "chrome/test/base/testing_profile.h"
 #include "components/data_reduction_proxy/core/browser/data_reduction_proxy_test_utils.h"
+#include "components/data_reduction_proxy/core/browser/data_store.h"
 #include "components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h"
 #include "components/data_reduction_proxy/core/common/data_reduction_proxy_params.h"
 #include "components/data_reduction_proxy/core/common/data_reduction_proxy_pref_names.h"
@@ -390,6 +391,8 @@ class RenderViewContextMenuPrefsTest : public ChromeRenderViewHostTestHarness {
     settings->InitDataReductionProxySettings(
         drp_test_context_->io_data(), drp_test_context_->pref_service(),
         drp_test_context_->request_context_getter(),
+        make_scoped_ptr(new data_reduction_proxy::DataStore()).Pass(),
+        base::ThreadTaskRunnerHandle::Get(),
         base::ThreadTaskRunnerHandle::Get());

[jeremyim, 2015/07/13 20:19:40]

It would be nice (but not necessary) if more of the boilerplate could be removed
(possibly by having drp_test_context_ expose a method to initialize an external
settings object).

[Not at Google. Contact bengr, 2015/07/14 16:41:30]

It seems confusing to have 2 settings objects, so I am hesitant to put code in
drp_test_context_ that encourages this.

Also, the DRPChromeSettings::InitDRPSettings is only called from this test, so
doesn't get us any reduction in total code lines.

Ideally, the builder would take an external DRPChromeSettings object.

[jeremyim, 2015/07/14 22:39:54]

I'm not looking for reduction in total code lines; I'm looking for a way that
changes in the way DRP classes are hooked up don't bleed into test code
(especially outside of the DRP component) and require updates elsewhere.

Having the builder take an external DRPChromeSettings seems like a great idea;
it might have solved the previous issues you had trying to get the test to work.
=)

[Not at Google. Contact bengr, 2015/07/15 00:08:17]

Sounds good. I'll do this in a separate cl.

[Not at Google. Contact bengr, 2015/07/15 22:34:09]

Jeremy: I investigated this further. Moving initialization of DRPChromeSettings
to DRPTestContext will add a dependency (in DRPTestContext) on the following
files:
       
'../chrome/browser/net/spdyproxy/data_reduction_proxy_chrome_settings.cc',
       
'../chrome/browser/net/spdyproxy/data_reduction_proxy_chrome_settings.h',
        '../chrome/common/pref_names.cc',
        '../chrome/common/pref_names.h',
        '../chrome/browser/browser_process.cc',
        '../chrome/browser/browser_process.h',
        '../chrome/browser/metrics/chrome_metrics_service_accessor.cc',
        '../chrome/browser/metrics/chrome_metrics_service_accessor.h',
        '../chrome/browser/profiles/profile.cc',
        '../chrome/browser/profiles/profile.h',
        '../chrome/browser/profiles/profile_manager.cc',
        '../chrome/browser/profiles/profile_manager.h',
        '../chrome/common/pref_names.cc',
        '../chrome/common/pref_names.h',
With this in mind, I don't think this is a good idea. What do you think?

   }