Add MemoryMonitorAndroid

content/browser/memory/memory_monitor_android_unittest.cc

+// Copyright (c) 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.
+
+#include "content/browser/memory/memory_monitor_android.h"
+
+#include "testing/gtest/include/gtest/gtest.h"
+
+namespace content {
+
+class MemoryMonitorAndroidTest : public testing::Test {
+ public:
+  MemoryMonitorAndroidTest() : monitor_(MemoryMonitorAndroid::Create()) {}
+
+ protected:
+  std::unique_ptr<MemoryMonitorAndroid> monitor_;
+};
+
+TEST_F(MemoryMonitorAndroidTest, CanGetMemoryInfo) {
+  EXPECT_TRUE(monitor_->CanGetMemoryInfo());
+}
+
+TEST_F(MemoryMonitorAndroidTest, GetMemoryInfo) {
+  MemoryMonitorAndroid::MemoryInfo info;
+  monitor_->GetMemoryInfo(&info);
+  EXPECT_GT(info.avail_mem, 0);
+  EXPECT_GT(info.threshold, 0);
+  EXPECT_GT(info.total_mem, 0);
+}

[chrisha, 2016/09/26 17:56:48]

A test of the actual GetFreeMemoryUntilCriticalMb logic as well?

[bashi, 2016/09/26 23:30:19]

In this test, GetFreeMemoryUntilCriticalMb() returns actual available memory on
the device on which this test is running and we can't specify an expected value
(it may be zero or even negative).

One option would be using a mock function (like other MemoryMonitor tests) but
what we want to test here is that checking whether JNI bindings and Android APIs
are working, so I didn't add a test of GetFreeMemoryUntilCriticalMb.

[chrisha, 2016/09/27 15:47:16]

I'd prefer we use a mock and test the actual logic as well, like the other
monitors.

[bashi, 2016/09/29 01:24:21]

Working on this.
https://codereview.chromium.org/2382623002/

+
+}  // namespace content