| include_rules = [ |
| # The test directory can do whatever it wants in chrome, and may |
| # rely on components. |
| "+ash", |
| "+chrome", |
| "+chrome/grit", |
| "+chromeos", |
| "+components", |
| "+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/ocmock", |
| "+third_party/webrtc", |
| ] |
