Create a field test for sync sign in promo strings.

chrome/browser/ui/webui/sync_setup_handler.cc

Index: chrome/browser/ui/webui/sync_setup_handler.cc
===================================================================
--- chrome/browser/ui/webui/sync_setup_handler.cc	(revision 111699)
+++ chrome/browser/ui/webui/sync_setup_handler.cc	(working copy)
@@ -384,6 +384,10 @@
     { "aspWarningText", IDS_SYNC_ASP_PASSWORD_WARNING_TEXT },
     { "promoPageTitle", IDS_SYNC_PROMO_TAB_TITLE},
     { "promoMessageBody", IDS_SYNC_PROMO_MESSAGE_BODY},
+    { "promoMessageBodyA", IDS_SYNC_PROMO_MESSAGE_BODY_A},

[sail, 2011/11/28 16:34:25]

instead of having multiple strings here and then doing a javascript call to
change the string it would be simpler to do something like this:
       SyncPromoUIHTMLSource::SyncPromoUIHTMLSource(WebUI* web_ui) {
         SyncSetupHandler::GetStaticLocalizedValues(&localized_strings)
         SyncPromoHandler::GetStaticLocalizedValues(&localized_strings, web_ui)
       }

       SyncSetupHandler::GetStaticLocalizedValues(DictionaryValue*
localized_strings, WebUI* web_ui) {
                if (IsInExperiment())
                                ...
        }
       }

If you could figure out a way to get rid of GetStaticLocalizedValues() and just
use GetLocalizedValues() then that would be even better!

[SteveT, 2011/11/28 20:07:32]

So I addressed this roughly in the way you suggested. It's not the tidiest
solution since we had to introduce a dependency on a WebUI object, and
NTPResourceCache is not capable of providing it (see my new TODO). Maybe
jhawkins has some suggestions on how to fix this.. plus the use of
GetStaticLocalizedValues.

+    { "promoMessageBodyB", IDS_SYNC_PROMO_MESSAGE_BODY_B},
+    { "promoMessageBodyC", IDS_SYNC_PROMO_MESSAGE_BODY_C},
+    { "promoMessageBodyD", IDS_SYNC_PROMO_MESSAGE_BODY_D},
     { "promoSkipButton", IDS_SYNC_PROMO_SKIP_BUTTON},
     { "promoAdvanced", IDS_SYNC_PROMO_ADVANCED},
     { "promoLearnMoreShow", IDS_SYNC_PROMO_LEARN_MORE_SHOW},