Move bluetooth API tests to //c/b/e/api/blueooth These two tests rely on //chrome components, in particular extension_apitest.cc. We no longer want to try to migrate these tests to extensions_browsertests, as those are based on app_shell. We don't want to bring up app_shell on desktop Android. Also, running tests under app_shell is not the best representation of how the API performs in chrome. So move the tests into //chrome and add them to browser_tests. Keep them both the same /api/bluetooth/ directory, as that's how they were structured before. Bug: 40425056 Change-Id: If0ef98e07bff98e50fbbc1207c3e3775de19b003 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6789390 Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/main@{#1493043}
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.