Switch over MobileActivator to use Network*Handler

chromeos/network/network_state.h

Index: chromeos/network/network_state.h
diff --git a/chromeos/network/network_state.h b/chromeos/network/network_state.h
index 03dcbb9dc956d663efee5bfe8571e7d44cdbe964..99a3a4b5c5a24ed5b42f3b0602682a4a3f466679 100644
--- a/chromeos/network/network_state.h
+++ b/chromeos/network/network_state.h
@@ -117,6 +117,7 @@ class CHROMEOS_EXPORT NetworkState : public ManagedState {
       const base::DictionaryValue& properties);
 
  private:
+  friend class MobileActivatorTest;

[armansito, 2013/08/14 00:49:51]

I see the convenience of making this a friend but is this absolutely necessary
and would it be hard to implement this test without it? (The same applies for
NetworkChangeNotifierChromeosUpdateTest below, though it's not related to this
CL).

[stevenjb, 2013/08/14 02:28:31]

I personally prefer using 'friend' for tests and keeping the members/accessors
private, assuming that the test actually needs access to them. (As opposed to
writing special ForTest accessors for trivial getters).

[gauravsh, 2013/08/14 21:42:29]

In this particular case, it's needed to manually set the state and
activation_state of a NetworkState.

Since there's a lot of precedent for the "friend class <TestFixture>" in the
chromium code base, I also find this preferable to adding a Set*ForTest to
NetworkState.

   friend class NetworkStateHandler;
   friend class NetworkChangeNotifierChromeosUpdateTest;