commit | 2cad1ef4618133dc45816fc0fa72ab983d00b6b9 | [log] [tgz] |
---|---|---|
author | Jérôme Lebel <jlebel@chromium.org> | Thu Mar 07 23:08:23 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 07 23:08:23 2024 |
tree | c5d6e3aa15ac1de07d665939b300b02ca641122a | |
parent | b378d23cfb8818d2a98a203ccc3da24aef684e9a [diff] |
[iOS][Waffle] Fix EGTest for search engine dialog This patch updates `[SettingsAppInterface resetSearchEngine]` to clear kDefaultSearchProviderChoiceScreenCompletionTimestamp pref. To make FirstRunWithSearchEngineChoiceTestCase tests more reliable, `[SettingsAppInterface resetSearchEngine]` is called in the setUp and the tearDown. This is to make sure those tests won't fail and to clean up after the tests. Same principal about setUp and tearDown is applied to `SearchEngineTestCase`. Therefore those EGTests can be enabled: SearchEngineTestCase/testOpenSecondWindow SearchEngineTestCase/testSearchEngineChoiceScreenSelectThenScroll SearchEngineTestCase/testSearchEngineChoiceScreenScrollThenSelect Bug: b/325441139 Change-Id: Ib6a60edf5011cccb45680121284289e9850faa77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5349529 Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Auto-Submit: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/main@{#1269888}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.