We'd like to eventually integrate DBW so it runs by default when you audit a page. There are open questions on doing so (gatherer pollution, how the new DevTools reporting will look).
Questions aside, the proposal here is to figure out how to run the tests together. I'd like to keep the existing dobetterweb.json config separate from the core default.json to maintain flexibility and not create/overload a monolithic config.
If the CLI accepted multiple configs, a default run of LH could look something like this under the hood:
npm run start -- --config-path=lighthouse-core/config/default.json --config-path=lighthouse-core/config/dobetterweb.json ...
Thoughts?
We'd like to eventually integrate DBW so it runs by default when you audit a page. There are open questions on doing so (gatherer pollution, how the new DevTools reporting will look).
Questions aside, the proposal here is to figure out how to run the tests together. I'd like to keep the existing dobetterweb.json config separate from the core default.json to maintain flexibility and not create/overload a monolithic config.
If the CLI accepted multiple configs, a default run of LH could look something like this under the hood:
Thoughts?