Switch to id-based affiliation determination

chrome/browser/chromeos/policy/blocking_login_browsertest.cc

Index: chrome/browser/chromeos/policy/blocking_login_browsertest.cc
diff --git a/chrome/browser/chromeos/policy/blocking_login_browsertest.cc b/chrome/browser/chromeos/policy/blocking_login_browsertest.cc
index 768bb466c1be66451b8066c8218984ded68c47b7..7c4041152ced29fe67adbf9eb43442c6c6cf77d6 100644
--- a/chrome/browser/chromeos/policy/blocking_login_browsertest.cc
+++ b/chrome/browser/chromeos/policy/blocking_login_browsertest.cc
@@ -243,8 +243,6 @@ IN_PROC_BROWSER_TEST_P(BlockingLoginTest, LoginBlocksForUser) {
     EXPECT_TRUE(browser_policy_connector()->IsEnterpriseManaged());
     EXPECT_EQ(kDomain, browser_policy_connector()->GetEnterpriseDomain());
     EXPECT_FALSE(profile_added_);
-    EXPECT_EQ(policy::USER_AFFILIATION_MANAGED,
-              browser_policy_connector()->GetUserAffiliation(kUsername));

[Andrew T Wilson (Slow), 2015/10/09 12:35:46]

Why is it OK to remove this? Should we do a different test instead
(user->isAffiliated())?

[peletskyi, 2015/10/29 15:27:37]

As far as I understood this line verifies domain, which was set in line 244 by
extracting it from kUsername. But currently we can not define domain judging by
user affiliation.

     RunUntilIdle();
     EXPECT_FALSE(user_manager->IsKnownUser(kUsername));
   }