mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-28 00:45:04 +08:00
Benedikt Meurer
4e8561d68f
Bug: b:325903709 Change-Id: If6f77c7fce0229e33f868cc18770050dfacc4195 Doc: http://go/chrome-devtools:move-unit-tests-design Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5321255 Commit-Queue: Kateryna Prokopenko <kprokopenko@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Kateryna Prokopenko <kprokopenko@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).