Pass --disable-field-trial-config to tests that need it.

Affected tests already run without the testing config applied,
so this CL makes it explicit.

Context: Browser tests that use ScopedFeatureList and pass
params presently cause the field trial testing config to be
entirely disabled. (details: crbug.com/1491463#c8)
We plan to fix this, but some existing tests rely on this
(fail with the testing config). This CL annotates those
tests explicitly by making them specify the flag for that.

Once all the CLs updating such tests land (sharded via git
cl split), the following CL to make ScopedFeatureList not
disable the testing config can land:
https://chromium-review.googlesource.com/c/chromium/src/+/4935093

As many tests are affected, it will be up to their owners
to do any necessary follow up if the tests should be made to
pass with the testing config (per the comments this CL adds).

Note: I did a best effort to have the new flag only apply to the
subset of tests that needed it when it was a single or a small
number of tests that were affected, by introducing subclasses
for the affected tests. In other cases, where lots of tests in
the same file fail, the flag is added to the original test class.

Note: The --disable-field-trial-config flag is passed simply
by name intentionally, to avoid additional complexity from
depending on components/variations and includes to reference
the existing constant for it. The name is unlikely to change and
this way, we need less complex code to add this to the tests.

This CL was uploaded by git cl split.

R=xinghuilu@chromium.org

Bug: 1491463
Change-Id: Ifc55418f755f1f25245838fdda2dde9bf8f3b6e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4935338
Auto-Submit: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Commit-Queue: Xinghui Lu <xinghuilu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1209586}
1 file changed
tree: d79e355b2084ceeb56fcf22d4abcac380939c2d5
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo 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.