include_rules = [
  # The test directory can do whatever it wants in chrome, and may
  # rely on components.
  "+ash",
  "+chrome",
  "+chrome/grit",
  "+chromeos",
  "+components/app_modal",
  "+components/autofill/content",
  "+components/autofill/core",
  "+components/bookmarks/browser",
  "+components/bookmarks/common",
  "+components/component_updater",
  "+components/constrained_window",
  "+components/content_settings/core/browser",
  "+components/crash/content/app",
  "+components/domain_reliability",
  "+components/download/public/common",
  "+components/favicon/core",
  "+components/google/core/common",
  "+components/guest_view/browser",
  "+components/history/content",
  "+components/history/core",
  "+components/infobars/core",
  "+components/keep_alive_registry",
  "+components/keyed_service/content",
  "+components/keyed_service/core",
  "+components/nacl/browser",
  "+components/nacl/common",
  "+components/nacl/renderer",
  "+components/network_time",
  "+components/offline_pages/buildflags",
  "+components/offline_pages/core",
  "+components/omnibox/browser",
  "+components/optimization_guide",
  "+components/os_crypt",
  "+components/policy",
  "+components/prefs",
  "+components/safe_browsing/buildflags.h",
  "+components/safe_browsing/db",
  "+components/search_engines",
  "+components/services/quarantine",
  "+components/signin/public",
  "+components/spellcheck",
  "+components/storage_monitor",
  "+components/subresource_filter/content/browser",
  "+components/sync/model",
  "+components/sync_preferences",
  "+components/unified_consent",
  "+components/update_client",
  "+components/user_manager",
  "+components/user_prefs",
  "+components/version_info",
  "+components/web_modal",
  "+components/webdata_services",
  "+components/zoom",
  "+device/bluetooth/dbus",
  "+extensions",
  "+mojo",
  "+rlz/buildflags",
  "+services",
  "+storage/browser",
  "+storage/common",

  # Tests under chrome/ shouldn't need to access the internals of content/ and
  # as such are allowed only content/public. If you find yourself wanting to
  # write such a test, or a test that depends primarily on content, think about
  # whether the test belongs under content/, or should be split up into a test
  # within content/ and a test within chrome/.
  "+content/public",

  "+gin/public",
  "+media/base",
  "+mojo/core/embedder",
  "+sandbox/win/tests",
  "+third_party/webrtc",
]
