Expose API to detect when captive portal probe was blocked on Android

net/android/network_library_unittest.cc

Index: net/android/network_library_unittest.cc
diff --git a/net/android/network_library_unittest.cc b/net/android/network_library_unittest.cc
new file mode 100644
index 0000000000000000000000000000000000000000..0cfec29394eebe1e7083485a7ef30d445a15fe12
--- /dev/null
+++ b/net/android/network_library_unittest.cc
@@ -0,0 +1,23 @@
+// 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.
+
+#include "net/android/network_library.h"
+
+#include "testing/gtest/include/gtest/gtest.h"
+
+namespace net {
+
+namespace android {
+
+namespace {

[pauljensen, 2016/11/24 00:11:19]

Remove the anonymous namespace

[tbansal1, 2016/11/24 00:43:09]

Done. Is this a //net specific guideline?
A cursory search on chromium-dev suggests that it is okay (if not preferable) to
put tests in anonymous namespaces.

https://groups.google.com/a/chromium.org/d/msg/chromium-dev/MwPIo2BnVhM/wvZxl...

https://groups.google.com/a/chromium.org/d/msg/chromium-dev/pKY2G4GHcu0/398sq...

[pauljensen, 2016/11/24 01:36:41]

I don't feel strongly.  There are pros and cons to both.

+
+TEST(NetworkLibraryTest, CaptivePortal) {
+  EXPECT_FALSE(android::GetIsCaptivePortal());
+}
+
+}  // namespace
+
+}  // namespace android
+
+}  // namespace net