Explicitly disable 3PCD in settings page tests that are for pre-3PCD - All components should have pre- and post-3PCD coverage (I have added some more for post-3PCD) - 3PCD state shouldn't matter for other test cases Here is a link to how fieldtrial_testing_config works: go/finch-fieldtrial-testing-config#effect-of-field-trial-testing-configs When we enable 3PCD in fieldtrial_testing_config we will get coverage for every code path with 3PCD on and off. So the explicit test cases we need are just for those that test explicit behavior that is only for pre- or post- 3PCD Bug: b:306414714 Change-Id: Ia057128a6e4984f4b99feea4b88e226014c1fba0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5014144 Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Auto-Submit: Fiona Macintosh <fmacintosh@google.com> Reviewed-by: Theodore Olsauskas-Warren <sauski@google.com> Cr-Commit-Position: refs/heads/main@{#1224274}
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.