Files
react-native-devtools-frontend/node_modules/axe-core/doc/examples/chrome-debugging-protocol
Tim van der Lippe 6d109a9d45 Update Mocha to 8.3.0
This also adds Python-2.0 to the list of accepted licenses.

Lastly, it fixes a bug where the package.json files were incorrectly
reordered. For the `exports` of a particular package, the order that
the entrypoints are defined in is crucial. Therefore, we should not
alter the order of entrypoints and instead maintain the originally
defined ordering. We can use an `OrderedDict` to ensure that Python
always loads the JSON files in the same order.

DISABLE_THIRD_PARTY_CHECK=NPM update
R=jacktfranklin@chromium.org

Bug: none
Change-Id: I5a309782de6015edea6ba3b502aa0db1f008d973
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2692909
Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
2021-02-17 12:08:49 +00:00
..
2021-02-17 12:08:49 +00:00

axe-chrome-debugging-protocol-example

This (very minimal) example demonstrates how to use axe-core with the Chrome Debugging Protocol.

The example does not have feature parity with axe-webdriverjs, and does not run on <iframe>s.

To run the example

  • Ensure Node v8+ is installed and on PATH
  • Move to the doc/examples/chrome-debugging-protocol directory
  • Run npm install
  • Run google-chrome --headless --remote-debugging-port=9222. If you don't have a google-chrome binary, you can alias one with alias google-chrome='/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome' on OSX.
  • Run node axe-cdp.js http://www.deque.com to run axe-core via Puppeteer against http://www.deque.com and output results to the terminal