Unittest for Component updater throttles

Unittest for Component updater throttles

Part of the on-demand feature see
https://codereview.chromium.org/25713007/ for more context.

BUG=none
TEST=none
R=sorin@chromium.org, waffles@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=236892

[cpu_(ooo_6.6-7.5), 2013-10-31 21:03:57]

Work in progress.

[Sorin Jianu, 2013-10-31 21:33:03]

lgtm

Thank you Carlos. I was thinking whether it would be worth testing that the on
demand request is being throttled, in other words that the virtuals on the
resource throttle object associated with the component are called. Also, it
seems we are only testing the NoUpdate case, would it be beneficial to test an
Update as well?

https://codereview.chromium.org/55303002/diff/1/chrome/browser/component_upda...
File chrome/browser/component_updater/test/component_updater_service_unittest.cc
(right):

https://codereview.chromium.org/55303002/diff/1/chrome/browser/component_upda...
chrome/browser/component_updater/test/component_updater_service_unittest.cc:1131:
// excersize the case where the component updater tries to use the weak
exercise

[cpu_(ooo_6.6-7.5), 2013-11-01 23:35:22]

Yeah, all of those will come.

[waffles, 2013-11-12 00:22:57]

lgtm

https://codereview.chromium.org/55303002/diff/1/chrome/browser/component_upda...
File chrome/browser/component_updater/test/component_updater_service_unittest.cc
(right):

https://codereview.chromium.org/55303002/diff/1/chrome/browser/component_upda...
chrome/browser/component_updater/test/component_updater_service_unittest.cc:1130:
// By requesting a throttle and deleting it immediately we insure that we
nitpicky: ensure.
Also on line 1185.

[cpu_(ooo_6.6-7.5), 2013-11-23 01:07:08]

Committed patchset #4 manually as r236892 (presubmit successful).