Use fake network connection tracker in browser tests on Fuchsia

The real network connection tracker never indicates that the browser is
online for Fuchsia. These tests don't actually care about online/offline
(that behavior is tested in the AttributionManagerImpl unit tests), so
we use a fake tracker that always indicates that the browser is online.

If the behavior on Fuchsia is ever changed, we will go back to using the
real tracker.

We change the AttributionManagerImpl to avoid injecting the tracker, and
instead retrieve it via content::GetNetworkConnectionTracker(), which
allows us to override it in attributions_browsertest.cc more easily via
content::SetNetworkConnectionTrackerForTesting().

Prior to crrev.com/c/3318796 these tests didn't fail because the
reporter assumed that the browser was online unless it heard otherwise,
whereas now the manager always queries the actual online status.

Bug: 1285057
Change-Id: Ifa765eab8435a5a4dc92631a8639096bc874b8a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3373141
Reviewed-by: John Delaney <johnidel@chromium.org>
Reviewed-by: Chong Gu <chonggu@google.com>
Commit-Queue: Andrew Paseltiner <apaseltiner@chromium.org>
Cr-Commit-Position: refs/heads/main@{#957390}
5 files changed
tree: 16f567aef6dd19301bbea43ee2250dc83e750876
  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. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. 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.