Google Git
Sign in
chromium / chromium / src / 70016448e6ab82000097bd4c7bbf15925894e555
commit70016448e6ab82000097bd4c7bbf15925894e555[log] [tgz]
authorDominic Battre <battre@chromium.org>Mon Oct 17 12:50:06 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Oct 17 12:50:06 2022
tree87a187442ff47a6b948fd07e885160b368992515
parent9a0735949dadbb33ee3653330be0745b9aab03dd [diff]
Move lists of test files to autofill directory

FormStructureBrowserTests on iOS differ from other platforms in that
they need a full list of testfiles listed in the BUILD.gn file. On
other plotforms, you just dump a new file into the directory and
everything works.

This has bugged me several times.
1) I typically add the files and later learn that iOS tests fail.
2) I need to find the right BUILD.gn file to add the new entry.
3) I need one more OWNERS approval.

Given that adding a file does not require any specific iOS expertise
I propose to move the list of test files closer to where the files
actually live and move them under the OWNERS purview of the
autofill team.

Fixed: 1374902
Change-Id: I068a119bf9c876dbbaac4869876c9a129d50231e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3956739
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Auto-Submit: Dominic Battré <battre@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1059903}
2 files changed
tree: 87a187442ff47a6b948fd07e885160b368992515
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.