Added UMA stats to track the budget for any service worker which receives a

chrome/browser/push_messaging/background_budget_service_unittest.cc

Index: chrome/browser/push_messaging/background_budget_service_unittest.cc
diff --git a/chrome/browser/push_messaging/background_budget_service_unittest.cc b/chrome/browser/push_messaging/background_budget_service_unittest.cc
index 501602881cd4def8dce4a089004b1cf294094aac..f09a396daa534ed1e67641b529a62f815447cee4 100644
--- a/chrome/browser/push_messaging/background_budget_service_unittest.cc
+++ b/chrome/browser/push_messaging/background_budget_service_unittest.cc
@@ -21,7 +21,7 @@ namespace {
 
 const char kTestOrigin[] = "https://example.com";
 const double kTestBudget = 10.0;
-const double kTestSES = 24.0;
+const double kTestSES = 48.0;
 const double kLowSES = 1.0;
 const double kMaxSES = 100.0;
 // Mirrors definition in BackgroundBudgetService, this is 10 days of seconds.
@@ -184,11 +184,13 @@ TEST_F(BackgroundBudgetServiceTest, GetBudgetConsumedOverTime) {
     budget = service->GetBudget(origin);
 
     if (i % 10 == 0) {
-      service->StoreBudget(origin, budget - 1.0);
+      double newBudget =

[Peter Beverloo, 2016/05/17 11:04:34]

nit: new_budget

[harkness, 2016/05/17 13:08:16]

actually, refactored a bit so renamed the variable.

+          budget - BackgroundBudgetService::GetBackgroundProcessingCost();
+      service->StoreBudget(origin, newBudget);
     }
   }
 
-  // With a SES of 24.0, the origin will get a budget of 2.4 per day, but the
+  // With a SES of 48.0, the origin will get a budget of 2.4 per day, but the
   // old budget will also decay. At the end, we expect the budget to be lower
   // than the starting budget.
   EXPECT_GT(budget, 0.0);