| commit | a9cb79034fb82f51a45342bc67f6dfeb83487839 | [log] [tgz] |
|---|---|---|
| author | Jesse McKenna <jessemckenna@google.com> | Fri May 31 21:12:31 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 31 21:12:31 2024 |
| tree | 83b6e6f05dc22f93bf54ebafb352189cdbc63dc8 | |
| parent | 65379ef0fd9ade0f5f23dde0d1c45ab8627ed931 [diff] |
breadcrumbs: re-enable failing tests This change fixes two tests that were flakily failing: BreadcrumbManagerTabHelperBrowserTest.Download BreadcrumbManagerTabHelperSecurityStateBrowserTest.BrokenAuthentication The tests expected that a certain amount of events would be logged during navigation, and made assertions about the content of the last-logged event. These tests were broken by some User-Education-related changes on 2024/1/8 that added more user actions (which are logged as breadcrumb events) during navigation. This CL fixes the tests by making less specific expectations about the number of logged events and their timing. In browser tests, we likely can't make precise assertions like "two breadcrumbs should have been logged", since that could change any time someone adds more user actions. The tests now simply check that the expected event was logged, which should make them more robust. Fixed: 1516817 Change-Id: Id92819c2a2718c74d63760e792fdaac72544be31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5585867 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: David Bienvenu <davidbienvenu@chromium.org> Commit-Queue: Jesse McKenna <jessemckenna@google.com> Cr-Commit-Position: refs/heads/main@{#1308894}
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.