readme: add gpu-benchmarking to cmd line flags. Indicate how to run tests.

This commit is contained in:
Paul Irish 2016-03-12 16:39:51 -08:00
Родитель 9a47535212
Коммит ea0c8a26d4
2 изменённых файлов: 11 добавлений и 9 удалений

Просмотреть файл

@ -35,8 +35,6 @@ class ChromeProtocol {
"disabled-by-default-devtools.screenshot",
"disabled-by-default-v8.cpu_profile"
];
// Add on GPU benchmarking.
// FIXME: --enable-gpu-benchmarking
}
requestTab(url) {

Просмотреть файл

@ -2,21 +2,25 @@
_status: very early. mostly not working_
## Running audits
## Running audits
Will run the audits defined in the `audits/` folder against a demo app. Chrome protocol connection maintained via [chrome-remote-interface](https://github.com/cyrus-and/chrome-remote-interface). Start Chrome manually; we can pursue [auto-launching](https://www.npmjs.com/package/chrome-launch) it later.
```sh
# Start Chrome with a few flags
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --remote-debugging-port=9222 --no-first-run --user-data-dir="/tmp/lighthouse-profile" "about:blank"
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --remote-debugging-port=9222 --no-first-run --user-data-dir="/tmp/lighthouse-profile" --enable-gpu-benchmarking "about:blank"
# Kick off a lighthouse run
node .
```
## Tests
Some basic unit tests forked from node-big-rig are in `/test` and run via mocha. eslint is also checked for style violations.
```js
npm test
```
## Trace processing
The traceviewer-based trace processor from [node-big-rig](https://github.com/GoogleChrome/node-big-rig/tree/master/lib) was forked into Lighthouse. It's exposed by `lib/processor`. See an example use in the [time-in-javascript](https://github.com/GoogleChrome/lighthouse/blob/85933f07791982d556177fddb55f578d30a4b56f/audits/time-in-javascript/index.js#L43) audit
## Tests
Some basic unit tests forked from node-big-rig are in `/test`. They may be broken.
The traceviewer-based trace processor from [node-big-rig](https://github.com/GoogleChrome/node-big-rig/tree/master/lib) was forked into Lighthouse. It's exposed by `lib/processor`. See an example use in the [time-in-javascript](https://github.com/GoogleChrome/lighthouse/blob/85933f07791982d556177fddb55f578d30a4b56f/audits/time-in-javascript/index.js#L43) audit