commit | 2aab5fe193496f00fc97ca5bf1e5391ee46d0fbe | [log] [tgz] |
---|---|---|
author | Arthur Milchior <arthurmilchior@chromium.org> | Mon Jan 20 14:02:53 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 20 14:02:53 2025 |
tree | 6098fe4a713f6b4b544529c1bf47a41577abf8d6 | |
parent | a26694a489af54071c1333e37c72606598369028 [diff] |
[iOS][Restore]Create an eg test for the restore promo This test ensures that, if Chrome starts with an account, and we simulate a post device restore, the promo to add back the account is opened, and the continue button open the add account view. This required a lot of preparation work. As far as I can see, promos were generally not tested. I hope this CL will show to to proceed to eg test them. I also need to ensure to add a test switch whose behavior is the same as the experimental flag to simulate post device restore. Indeed, we want to test the same feature. I need to sign-in at startup. Which currently most work after a restart and not the initial start. Given that this alert is implemented as a promo, I also needed to use `kEnableIPH` to allow this promo to be enabled. By default, they all are disabled in eg tests. To be more specific, they are all disabled by two switches. I removed the second and redundant switch in crrev.com/c/6172453. Change-Id: Ia4f8a35fcf226babfa1cda575a8e22a688c18a6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6170430 Reviewed-by: Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Arthur Milchior <arthurmilchior@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Auto-Submit: Arthur Milchior <arthurmilchior@chromium.org> Reviewed-by: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/main@{#1408636}
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.