summaryrefslogtreecommitdiff
path: root/tests/common/java/android/net/NetworkCapabilitiesTest.java
diff options
context:
space:
mode:
authorAaron Huang <huangaaron@google.com>2021-11-09 15:50:42 +0800
committerAaron Huang <huangaaron@google.com>2021-11-15 20:01:12 +0800
commite3879abb076e4798523c96eda63e9fcb3bd622ae (patch)
tree45254d25828505f6c68a82d8a9d638fbb136590a /tests/common/java/android/net/NetworkCapabilitiesTest.java
parentff8169207713cb447d59df13aabf670b0f74ee5a (diff)
Use real ProxyTracker in ConnectivityServiceTest
Currently CS test uses a mock ProxyTracker object to verify that the sendProxyBroadcast() is called. Also, if the network is a default network then sendProxyBroadcast() will be indirectly called in setDefaultProxy(). This only verifies that the method is called but it doesn't verify that the broadcast is sent. Instead of testing setDefaultProxy() is called, it is better to verify that the broadcast is actually sent. Therefore, use a real ProxyTracker in the test to verify the broadcast is sent. Test: FrameworksNetTests:ConnectivityServiceTest Change-Id: Id5c9e07e8326f24bd2665b4bb08f96d6d57d999c
Diffstat (limited to 'tests/common/java/android/net/NetworkCapabilitiesTest.java')
0 files changed, 0 insertions, 0 deletions