[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 9fdf1bc5c13141b4a2dd46d4c040302b103a242c
commit9fdf1bc5c13141b4a2dd46d4c040302b103a242c[log] [tgz]
authorJack Franklin <jacktfranklin@chromium.org>Wed Mar 01 16:40:07 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 02 09:31:09 2023
tree55be0a4a4895ca0326da4979cbf1895ab98c0a0f
parent3e218b2909cbe0a300fb7f7f71ebb973306ca0e8 [diff]
Automatically reset trace handlers in tests

This CL automatically resets trace handlers between tests so we know
that no data is leaking into other tests. I then found some tests that
needed fixing, and I also updated the network handler to have an
explicit initialize step, which brings it inline with the other
handlers and makes it easier to test.

Bug: none
Change-Id: I0f1c055658b8639274406ee392bfb773938957f3
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4300469
Reviewed-by: Andres Olivares <andoli@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
6 files changed
tree: 55be0a4a4895ca0326da4979cbf1895ab98c0a0f
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .mailmap
  22. .npmignore
  23. .npmrc
  24. .style.yapf
  25. .stylelintignore
  26. .stylelintrc.json
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

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.

Additional references

Source mirrors

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.

Getting in touch