mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-30 09:17:09 +08:00
Benedikt Meurer
70710c8820
Previously we had a lot of documentation bundled in the `workflows.md` file, which wasn't necessarily obvious to new users. The getting the code documentation now lives in a dedicated file `get_the_code.md`, which is also directly linked from the toplevel `README.md`, since that's what developers are looking first. It also rearranges the rest of the project documentation a bit to move the most important things to the top, add [TOC]s everywhere and streamlines the documentation around (3rd party) dependencies, as well as updating the documentation on testing. Bug: none Change-Id: I7b5d9121c7f1137eeff7a4ff159816908ef10705 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4931037 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
1.2 KiB
1.2 KiB
Testing Chromium DevTools
Follow the steps outlined in Get the Code to checkout the DevTools front-end code.
[TOC]
DevTools frontend
Test are available by running scripts in scripts/test/. Please refer to the overview document. The current test status can be seen at the test waterfall.
Layout tests
After building content shell as part of Chromium, we can also run layout tests that are relevant for DevTools frontend:
autoninja -C out/Default content_shell
third_party/blink/tools/run_web_tests.py -t Default http/tests/devtools
To debug a failing layout test we can run
npm run debug-test -- http/tests/devtools/<path>/<to>/<test>.js
The script supports either default DevTools checkout inside the chromium tree or side-by-side checkouts of chromium and DevTools. Passing --custom-devtools-frontend is not supported currently, meaning in the side-by-side scenario the DevTools checkout inside the chromium tree will be used (if not symlinked).