diff options
author | pastarmovj@chromium.org <pastarmovj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-17 12:11:19 +0000 |
---|---|---|
committer | pastarmovj@chromium.org <pastarmovj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-17 12:11:19 +0000 |
commit | fd8c8b580022c46e335709047f845d592d3cf850 (patch) | |
tree | 6dd7148c65f2207d2e0c9f5eb5a03a280d4ecf35 /sync | |
parent | 39e5b0934ce0cf3adecb36afa9d4116afc2f8e18 (diff) | |
download | chromium_src-fd8c8b580022c46e335709047f845d592d3cf850.zip chromium_src-fd8c8b580022c46e335709047f845d592d3cf850.tar.gz chromium_src-fd8c8b580022c46e335709047f845d592d3cf850.tar.bz2 |
Fix the unit test to run in a clean profile dir and add a new test to check proper migration.
The test was not producing correct results on one of the bots because the pref
checked has a special migration path that might populate it even if not set in the
policy file. To avoid this we run all tests from this group in a clean profile
directory and also to make sure migration works as expected I added a new test
to the suit too.
BUG=148356
TEST=unit_tests: DeviceSettingsProviderTest.SetPrefFailed should pass on all bots.
Review URL: https://chromiumcodereview.appspot.com/10916288
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157107 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync')
0 files changed, 0 insertions, 0 deletions