[Sync] Add diagnostic into AndroidSyncSettingsTest

[Sync] Add diagnostic into AndroidSyncSettingsTest

After my last change tests started failing on assert in setUp claiming that
getIsSyncable returns -1.

I'm trying to confirm if code in AndroidSyncSettings.updateSyncability executes
call to setIsSyncable, thus adding a few assertTrue.

In addition I noticed that AndroidSyncSettings.mContractAuthority is initialized
in ctor, but getContractAuthority() still calls mApplicationContext. I changed
it to always return mContractAuthority to ensure the same value is used
throughout test execution.

BUG=717960
R=skym@chromium.org

Review-Url: https://codereview.chromium.org/2873893004
Cr-Commit-Position: refs/heads/master@{#470697}
Committed: https://chromium.googlesource.com/chromium/src/+/78577b17b468843edb79d4111471b16e55e2aaac

[pavely, 2017-05-10 18:59:28]

The CQ bit was checked by pavely@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-10 19:03:49]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[skym, 2017-05-10 19:50:16]

lgtm

[pavely, 2017-05-10 19:51:16]

The CQ bit was unchecked by pavely@chromium.org

[pavely, 2017-05-10 19:51:17]

The CQ bit was checked by pavely@chromium.org

[commit-bot: I haz the power, 2017-05-10 19:52:15]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-10 20:40:53]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494445877634950, "parent_rev":
"a329ea3b2bc1be1519f6a22ac757e55ba0cc922a", "commit_rev":
"78577b17b468843edb79d4111471b16e55e2aaac"}

[commit-bot: I haz the power, 2017-05-10 20:41:07]

Description was changed from

==========
[Sync] Add diagnostic into AndroidSyncSettingsTest

After my last change tests started failing on assert in setUp claiming that
getIsSyncable returns -1.

I'm trying to confirm if code in AndroidSyncSettings.updateSyncability executes
call to setIsSyncable, thus adding a few assertTrue.

In addition I noticed that AndroidSyncSettings.mContractAuthority is initialized
in ctor, but getContractAuthority() still calls mApplicationContext. I changed
it to always return mContractAuthority to ensure the same value is used
throughout test execution.

BUG=717960
R=skym@chromium.org
==========

to

==========
[Sync] Add diagnostic into AndroidSyncSettingsTest

After my last change tests started failing on assert in setUp claiming that
getIsSyncable returns -1.

I'm trying to confirm if code in AndroidSyncSettings.updateSyncability executes
call to setIsSyncable, thus adding a few assertTrue.

In addition I noticed that AndroidSyncSettings.mContractAuthority is initialized
in ctor, but getContractAuthority() still calls mApplicationContext. I changed
it to always return mContractAuthority to ensure the same value is used
throughout test execution.

BUG=717960
R=skym@chromium.org

Review-Url: https://codereview.chromium.org/2873893004
Cr-Commit-Position: refs/heads/master@{#470697}
Committed:
https://chromium.googlesource.com/chromium/src/+/78577b17b468843edb79d4111471...
==========

[commit-bot: I haz the power, 2017-05-10 20:41:13]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/78577b17b468843edb79d4111471...