Add unit tests for the Background Scheduler.

chrome/android/junit/src/org/chromium/chrome/browser/offlinepages/BackgroundOfflinerTaskTest.java

Index: chrome/android/junit/src/org/chromium/chrome/browser/offlinepages/BackgroundOfflinerTaskTest.java
diff --git a/chrome/android/junit/src/org/chromium/chrome/browser/offlinepages/BackgroundOfflinerTaskTest.java b/chrome/android/junit/src/org/chromium/chrome/browser/offlinepages/BackgroundOfflinerTaskTest.java
new file mode 100644
index 0000000000000000000000000000000000000000..dbd44d6c80211b6d2cd4ba7e0c221aa1d5fcff0f
--- /dev/null
+++ b/chrome/android/junit/src/org/chromium/chrome/browser/offlinepages/BackgroundOfflinerTaskTest.java
@@ -0,0 +1,59 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+package org.chromium.chrome.browser.offlinepages;
+
+import static org.junit.Assert.assertTrue;
+
+import android.os.Bundle;
+
+import org.chromium.base.BaseChromiumApplication;
+import org.chromium.base.test.util.Feature;
+import org.chromium.testing.local.LocalRobolectricTestRunner;
+import org.junit.Before;
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.robolectric.annotation.Config;
+
+import java.util.Date;
+
+/**
+ * Unit tests for BackgroundOfflinerTask.
+ */
+@RunWith(LocalRobolectricTestRunner.class)
+@Config(manifest = Config.NONE,
+        application = BaseChromiumApplication.class)
+public class BackgroundOfflinerTaskTest {
+    private Bundle mTaskExtras;
+    private long mTestTime;
+    private StubBackgroundSchedulerBridge mStubBackgroundSchedulerBridge;
+
+    @Before
+    public void setUp() throws Exception {
+        // Build a bundle
+        mTaskExtras = new Bundle();
+        // TODO: Replace time with ticks since boot
+        Date now = new Date();
+        mTestTime = now.getTime();
+        mTaskExtras.putLong(BackgroundScheduler.DATE_TAG, mTestTime);
+        mStubBackgroundSchedulerBridge = new StubBackgroundSchedulerBridge();
+    }
+
+    @Test
+    @Feature({"OfflinePages"})
+    public void testIncomingTask() {
+        BackgroundOfflinerTask task =
+                new BackgroundOfflinerTask(mStubBackgroundSchedulerBridge);
+        task.onProcessingDone(true);

[dougarnett, 2016/06/02 16:31:47]

why calling done callback first?

[Pete Williamson, 2016/06/02 20:51:33]

Originally it was to release the latch and let the call proceed.  The
CountDownLatch moved to another changelist, but this stayed here, and at least
makes sure onProcessingDone() gets called from the tests.  I can remove it if
you like (but it may have to come back later)

+        task.processBackgroundRequests(mTaskExtras);
+
+        // Check with ShadowBackgroundSchedulerBridge that startProcessing got called.
+        assertTrue(mStubBackgroundSchedulerBridge.getStartProcessingCalled());
+    }
+
+    @Test
+    @Feature({"OfflinePages"})
+    public void testOnProcessingDone() {

[dougarnett, 2016/06/02 16:31:47]

TODO here or instead since this isn't actually testing anything yet

[Pete Williamson, 2016/06/02 20:51:33]

Done.

+    }
+}