Remove assumption about initial ordinals in app sync tests

chrome/browser/sync/test/integration/two_client_apps_sync_test.cc

Index: chrome/browser/sync/test/integration/two_client_apps_sync_test.cc
diff --git a/chrome/browser/sync/test/integration/two_client_apps_sync_test.cc b/chrome/browser/sync/test/integration/two_client_apps_sync_test.cc
index 782a63535ecf6187435cd45f78c0d5ff77e68951..ea6efc3f4ebac40b1fb980446183051aaf0a2854 100644
--- a/chrome/browser/sync/test/integration/two_client_apps_sync_test.cc
+++ b/chrome/browser/sync/test/integration/two_client_apps_sync_test.cc
@@ -369,7 +369,10 @@ IN_PROC_BROWSER_TEST_F(TwoClientAppsSyncTest, UpdateAppLaunchOrdinal) {
   ASSERT_TRUE(AllProfilesHaveSameAppsAsVerifier());
 
   syncer::StringOrdinal initial_position =
-      syncer::StringOrdinal::CreateInitialOrdinal();
+    GetProfile(0)->GetExtensionService()->extension_prefs()

[akalin, 2012/11/22 09:34:33]

i think a more robust solution would be to get the ordinal of the app after it's
installed and then use that instead of relying on it being the first app
installed.

Can you add a GetAppLaunchOrdinalForApp(Profile*, int) function (similar to
SetAppLaunchOrdinalForApp below) and use that in this test instead?

+      ->extension_sorting()->CreateFirstAppLaunchOrdinal(
+          syncer::StringOrdinal::CreateInitialOrdinal());
+
   InstallApp(GetProfile(0), 0);
   InstallApp(GetProfile(1), 0);
   InstallApp(verifier(), 0);