Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/authentication
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/bookmarks', 'ios/chrome/browser/main', 'ios/chrome/browser/save_to_drive', 'ios/chrome/browser/intelligence', 'ios/chrome/browser/ntp', 'ios/chrome/browser/push_notification', 'ios/chrome/browser/safety_check', 'ios/chrome/browser/tabs_search', 'ios/chrome/browser/tips_notifications']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/bring_android_tabs', 'ios/chrome/browser/lens_overlay', 'ios/chrome/browser/shared', 'ios/chrome/browser/content_suggestions', 'ios/chrome/browser/overlays', 'ios/chrome/browser/promos_manager', 'ios/chrome/browser/save_to_photos', 'ios/chrome/browser/tab_switcher']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/browser_view', 'ios/chrome/browser/enterprise', 'ios/chrome/browser/account_picker', 'ios/chrome/browser/browsing_data', 'ios/chrome/browser/location_bar', 'ios/chrome/browser/post_restore_signin', 'ios/chrome/browser/safe_browsing', 'ios/chrome/browser/signin', 'ios/chrome/browser/welcome_back']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/download
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/drive_file_picker', 'ios/chrome/browser/reader_mode', 'ios/chrome/browser/autofill', 'ios/chrome/browser/commerce', 'ios/chrome/browser/popup_menu', 'ios/chrome/browser/prerender', 'ios/chrome/browser/saved_tab_groups', 'ios/chrome/browser/synced_set_up']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/ntp/ui_bundled
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/settings
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Marc Treib would like Rohit Rao to review this change.
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/settings/ui_bundled/password
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/bookmarks', 'ios/chrome/browser/main', 'ios/chrome/browser/save_to_drive', 'ios/chrome/browser/intelligence', 'ios/chrome/browser/ntp', 'ios/chrome/browser/push_notification', 'ios/chrome/browser/safety_check', 'ios/chrome/browser/tabs_search', 'ios/chrome/browser/tips_notifications']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/authentication
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/settings/ui_bundled/password
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
#import "ios/chrome/browser/signin/model/identity_test_environment_browser_state_adaptor.h"Is this needed?
#import "components/sync/test/test_sync_service.h"Is this needed, if we're using a real SyncService in this test?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/ntp/ui_bundled
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
R=rohi...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/bring_android_tabs', 'ios/chrome/browser/lens_overlay', 'ios/chrome/browser/shared', 'ios/chrome/browser/content_suggestions', 'ios/chrome/browser/overlays', 'ios/chrome/browser/promos_manager', 'ios/chrome/browser/save_to_photos', 'ios/chrome/browser/tab_switcher']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/download
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +0 |
| Commit-Queue | +1 |
public_deps = [Marc TreibWhy public_deps?
No good reason, really - without this, the `unit_tests` target also has to depend on sync, but that's better. Updated.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +0 |
| Commit-Queue | +1 |
#import "ios/chrome/browser/signin/model/identity_test_environment_browser_state_adaptor.h"Marc TreibIs this needed?
Nope, dunno where that came from, sorry!
Is this needed, if we're using a real SyncService in this test?
Nope! Removed.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
1 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: ios/chrome/browser/safe_browsing/model/tailored_security/tailored_security_tab_helper_unittest.mm
Insertions: 0, Deletions: 1.
The diff is too large to show. Please review the diff.
```
```
The name of the file: ios/chrome/browser/enterprise/model/idle/action_unittest.mm
Insertions: 0, Deletions: 1.
The diff is too large to show. Please review the diff.
```
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/browser_view', 'ios/chrome/browser/enterprise', 'ios/chrome/browser/account_picker', 'ios/chrome/browser/browsing_data', 'ios/chrome/browser/location_bar', 'ios/chrome/browser/post_restore_signin', 'ios/chrome/browser/safe_browsing', 'ios/chrome/browser/signin', 'ios/chrome/browser/welcome_back']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
ios/chrome/browser/settings
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
1 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: ios/chrome/browser/reader_mode/model/BUILD.gn
Insertions: 6, Deletions: 6.
The diff is too large to show. Please review the diff.
```
[iOS] Update unit tests to create TestSyncService/SyncServiceImpl
Before, many unit tests on iOS relied (often accidentally) on the
fact that the SyncServiceFactory will, by default, create a real
SyncServiceImpl, even in unit tests.
Most of these tests don't actually need a real SyncServiceImpl;
they just need "something that's not null". This is better served
by TestSyncService, and so most tests are updated to use that. A
few tests *do* need SyncServiceImpl, and are updated to set that
up explicitly.
This CL addresses test files in the following directory/ies:
['ios/chrome/browser/drive_file_picker', 'ios/chrome/browser/reader_mode', 'ios/chrome/browser/autofill', 'ios/chrome/browser/commerce', 'ios/chrome/browser/popup_menu', 'ios/chrome/browser/prerender', 'ios/chrome/browser/saved_tab_groups', 'ios/chrome/browser/synced_set_up']
In a later CL, the factory will be updated to specify
TestingCreation::kNoServiceForTests, so that all future tests
will have to specify which kind of SyncService they need. This
will bring the iOS factory in line with that for other platforms
(see SyncServiceFactory::ServiceIsNULLWhileTesting()).
This CL was uploaded by git cl split.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |