[i18n] components directory to $i18n{}

components/supervised_user_error_page/supervised_user_error_page_unittest.cc

Index: components/supervised_user_error_page/supervised_user_error_page_unittest.cc
diff --git a/components/supervised_user_error_page/supervised_user_error_page_unittest.cc b/components/supervised_user_error_page/supervised_user_error_page_unittest.cc
index 7565ff4b03d407b7577f517c7a2cc7fe20b93179..41a60493733853b81a89451b94a9cb8502febfd7 100644
--- a/components/supervised_user_error_page/supervised_user_error_page_unittest.cc
+++ b/components/supervised_user_error_page/supervised_user_error_page_unittest.cc
@@ -76,14 +76,10 @@ TEST_P(SupervisedUserErrorPageTest_BuildHtml, BuildHtml) {
       param.profile_image_url2, param.custodian, param.custodian_email,
       param.second_custodian, param.second_custodian_email,
       param.is_child_account, param.reason, "");
-  // The result should contain the original HTML plus scripts that plug values
-  // into it. The test can't easily check that the scripts are correct, but
-  // can check that the output contains the expected values.
-  std::string html =
-      ResourceBundle::GetSharedInstance()
-          .GetRawDataResource(IDR_SUPERVISED_USER_BLOCK_INTERSTITIAL_HTML)
-          .as_string();
-  EXPECT_THAT(result, testing::HasSubstr(html));

[dschuyler, 2017/05/31 21:10:53]

This was previously testing that BuildHtml and GetRawDataResource would load the
same IDR_SUPERVISED_USER_BLOCK_INTERSTITIAL_HTML text. That assumption doesn't
hold in the the $i18n{} world, because the i18n is inlined immediately (that's
the power of $i18n{}, i.e. why it exists). I considered what it would mean to
keep this comparison, but it would end up being a second call to BuildHtml()
(i.e. testing that "BuildHtml(...) == BuildHtml(...)" which isn't a valuable
comparison.

[tommycli, 2017/06/12 18:49:20]

Agreed, let's just axe that above EXPECT clause. ^

Thanks for the thorough explanation.

[tommycli, 2017/06/12 18:52:05]

I looked into it some more out of curiosity. Previous test was pretty much
tautological anyways. No loss in removal IMO.

+  // The result should contain the original HTML (with $i18n{} replacements)
+  // plus scripts that plug values into it. The test can't easily check that the
+  // scripts are correct, but can check that the output contains the expected
+  // values.
   EXPECT_THAT(result, testing::HasSubstr(param.profile_image_url));
   EXPECT_THAT(result, testing::HasSubstr(param.profile_image_url2));
   EXPECT_THAT(result, testing::HasSubstr(param.custodian));