[web tests] Remove all web tests from DevTools repository After migrating the tests to the Chromium repository and removing the step that runs these tests on the DevTools bot, we can now remove the web tests from the DevTools frontend. The initial experiment was to see if it's feasible to host the DevTools related web tests directly in the DevTools repository. But we'd lose too much coverage (dfferent platfroms/configs/etc). In the end we decided to keep DevTools web tests in the Chromium repo and focused more on DevTools e2e tests. R=dsv@chromium.org Fixed: 1447470 Change-Id: I3b6830a57d64fbd3b7351b1d1bdc202165553fea Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4547510 Commit-Queue: Simon Zünd <szuend@chromium.org> Auto-Submit: Simon Zünd <szuend@chromium.org> Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Danil Somsikov <dsv@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools