
This relands commite7481c5056
. Which was reverted in commitdc8e02663b
. There was an issue in the original CL where the argument --test_policy_to_pref_mappings_filter gets popuplated when there are no policy pref mapping test files. This wasn't noticed because c++ unit tests and browser tests ignore this flag and work correctly. Android tests OTOH throw an error because the flag is unknown. This CL filters policy pref mapping files when building the flag. Original change's description: > autotest.py: Support policy to pref mappings tests > > Pref mapping test files now work, for example: > $ tools/autotest.py -C out/Default \ > components/policy/test/data/pref_mapping/NewWindowsInKioskAllowed.json > $ tools/autotest.py -C out/Default \ > components/policy/test/data/pref_mapping \ > --test_policy_to_pref_mappings_filter=NewWindowsInKioskAllowed > > Which are equivalent to: > $ autoninja -C out/Default browser_tests > $ out/Default/browser_tests \ > --gtest_filter="*PolicyPrefsTest.PolicyToPrefsMapping" \ > --test_policy_to_pref_mappings_filter="NewWindowsInKioskAllowed" > > Bug: b:319254568 > Test: tools/autotest.py -C out/Default components/policy/test/data/pref_mapping > Test: tools/autotest.py -C out/Default components/policy/test/data/pref_mapping/NewWindowsInKioskAllowed.json > Change-Id: I8eb36a69abd717bf69c56a7f1aa453209c3da5a2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5185801 > Reviewed-by: Maksim Ivanov <emaxx@chromium.org> > Reviewed-by: Michael Thiessen <mthiesse@chromium.org> > Commit-Queue: Edman Anjos <edman@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1254565} Bug: b:319254568 Change-Id: I4f3aab804b27ae5939a87804be270b15304d8561 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5257580 Reviewed-by: Maksim Ivanov <emaxx@chromium.org> Reviewed-by: Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Edman Anjos <edman@chromium.org> Cr-Commit-Position: refs/heads/main@{#1255138}
Chromium
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.