Move ContentScriptMatchingBrowserTest to browser_tests From its old home of from extensions_browsertests. This test covers interaction of content scripts, frame trees and ScriptInjectionTracker. Running it as part of chrome's browser_tests is a more realistic simulation of its production behavior. (Plus, we would like to deprecate extensions_browsertests.) This CL moves the ContentScriptMatchingBrowserTest to //chrome/browser, so it's closer to where similar tests are and so that we can take advantage of ChromeTestExtensionLoader and other chrome/browser-only fixtures. Bug: none Change-Id: I9eceb41844251887e2d013d05e971301f8345e84 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6786411 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by: Zhengzheng Liu <zhzhliu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1492254}
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.