Google Git
Sign in
chromium / chromium / src / 1667cd2febb8dd11eeb9c24ef726cd80210e5ae2
commit1667cd2febb8dd11eeb9c24ef726cd80210e5ae2[log] [tgz]
authorSven Zheng <svenzheng@chromium.org>Wed Sep 02 18:25:51 2020
committerCommit Bot <commit-bot@chromium.org>Wed Sep 02 18:25:51 2020
tree412c9335430a63ef7ed8603ccf0a0b9b2c9b6c86
parentacbc2641b4ebdf041b8453ae386922b8f89c90e5 [diff]
Get the first sync test work on Android

This cl get SingleClientTypedUrlsSyncTest works on Android. Clank
doesn't support multiple profiles, and all sync tests need multiple
profiles. For single client test on desktop, it need at least 2 profiles:
1 The default browser and profile, started by browser test;
2 The browser and profile under test, created by AddBrowser();
3 If verifier is enabled, create another verifier profile.
For Android, we can't do that. This cl does:
* Only support single client test on Android.
* For 1 and 2, we only use the default browser and profile as SUT.
* For 3, we don't support it for Android.

android_sync_integration_tests.
$ autoninja -C out/Clank android_sync_integration_tests
$ out/Clank/android_sync_integration_tests

TEST: Locally tested on a Next 5X device for target
BUG: 1117345
Change-Id: I0167164334fc63be5cc278c145daf130ba16912e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387404
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Sven Zheng <svenzheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#803930}
1 file changed
tree: 412c9335430a63ef7ed8603ccf0a0b9b2c9b6c86
  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. cloud_print/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  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.

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.