Simple offline startup integration test.

Simple offline startup integration test.
This is a simple offline startup integration test.  This change also includes the groundwork for more complex offline startup test cases, including the ability to enable and disable network connectivity as well as configure the mock sync server with a username.

BUG=47918
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=56087

[skrul, 2010-08-06 20:13:15]

Raghu -- I'm sending this for early review with just a simple offline statup
test just to see if you agree with the way I'm going about it.  I will have a
follow up change that is a bit more complex (start online then restart offline,
then go online).

[Raghu Simha, 2010-08-10 00:14:57]

This is a great start. I had a couple of questions re: how this would work when
we use an external test sync server (instead of a local python sync server).

http://codereview.chromium.org/3078031/diff/1/3
File chrome/test/live_sync/live_sync_test.cc (right):

http://codereview.chromium.org/3078031/diff/1/3#newcode291
chrome/test/live_sync/live_sync_test.cc:291: std::string url =
StringPrintf("http://%s:%d/chromiumsync/configure",
This code will work only if the tests are run against a local python sync
server, which runs with the URL "http://127.0.0.1:9443/chromiumsync". However,
our tests are also wired to be able to run against a real sync server, whose URL
might be passed in via the --sync-url flag. See the call to
SetUpLocalTestServer() in this file.

In order to not break the external sync server scenario, we'll need to check if
kSyncServiceURL has been passed in. (I'm assuming the real server does support
what you are doing here, correct?)

And in case this kind of configuration is supported only by the python sync
server, we'll need to disable the offline tests when they are run against an
external sync server.

http://codereview.chromium.org/3078031/diff/1/6
File chrome/test/live_sync/profile_sync_service_test_harness.cc (right):

http://codereview.chromium.org/3078031/diff/1/6#newcode282
chrome/test/live_sync/profile_sync_service_test_harness.cc:282: "Waiting for
OnBackendInitialized().")) {
Is OnBackendInitialized() guaranteed to be triggered when a re-auth is done? If
not, we could end up waiting a really long time here. (If it is guaranteed,
we're fine here.)

http://codereview.chromium.org/3078031/diff/1/7
File chrome/test/live_sync/profile_sync_service_test_harness.h (right):

http://codereview.chromium.org/3078031/diff/1/7#newcode112
chrome/test/live_sync/profile_sync_service_test_harness.h:112: bool
WaitForServiceInit(bool is_auth_retry);
nit: Could you add a comment for what "is_auth_retry" is used for?

[Raghu Simha, 2010-08-13 20:41:26]

LGTM.