Amanda Baker
06da915c02
After submiting accessbility fixes for the Sensors tool and Performance Monitor, we should aim to not regress these improvements. This change adds the AxeCoreTestRunner module which uses aXe to run basic accessbility checks on the UI. It also adds a test that runs aXe against the Performance Monitor and Sensors tool since they have already received an initial accessibility pass and are not reporting any violations in aXe. Change-Id: I6443d5014d9200a9295746aaec7a71b4659a6417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534551 Reviewed-by: Joel Einbinder <einbinder@chromium.org> Commit-Queue: Amanda Baker <ambake@microsoft.com> Cr-Original-Commit-Position: refs/heads/master@{#645823} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: f854b6f5a7a1e16fe5880c40e8055e92eca37943
DevTools Scripts
Development workflow scripts
These are scripts that can be useful to run independently as you're working on Chrome DevTools front-end.
The newer scripts such as for testing and hosted mode are written in Node.js, which has become the standard toolchain for web apps. The older scripts such as building (e.g. bundling and minifying) are written in Python, which has first-class support in Chromium's infrastructure.
Overview
Folders
- build - Python package for generating DevTools debug and release mode
- chrome_debug_launcher - automagically finds Chrome Canary and launches it with debugging flags (e.g. remote debugging port)
- closure - see section on Closure Compiler below
- gulp - experimental build process written in node.js & gulp to remove the dependency on Chromium-specific build tools (i.e. gn and ninja)
- hosted_mode - run DevTools on a localhost development server
- jsdoc_validator - enforces the use of Closure type annotations
- local_node - installs a local runtime of node.js
Python Scripts
- convert_svg_images_to_png.py - manually run when adding svg images
- compile_frontend.py - runs closure compiler to do static type analysis
- Note: the compiled outputs are not actually used to run DevTools
- lint_javascript.py - run eslint
- optimize_png_images.py - manually run when adding png images
Node.js scripts
The easiest way to run the node.js scripts is to use npm run which displays all the commands. For more information on the specific npm run commands, take a look at the primary devtools front-end readme (../readme.md).
Closure
DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective directory.