Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 2: Add support for running lighthouse tests locally #9

Merged
merged 5 commits into from Mar 21, 2024
Merged

Conversation

mattheu
Copy link
Member

@mattheu mattheu commented Oct 24, 2023

I've made a few improvements to this.

  • Option to run tests using a locally installed version of lighthouse. A big limitation right now is that it can only check publicly facing pages as it relies on the Google Pagespeed API to get results. This change means that you can run the exact same test with a locally installed version of lighthouse. In my testing, I'm not really seeing more noticable variance in results using this over pagespeed which was a big reason I used the API previously. The downside is that it can't run tests in parallel which the pagespeed API can do so is slower for a lot URLs. Select the method using the engine property in the config. Either pagespeed or lighthouse.
  • Allow for configuration per group. Previously supported groups of URLs e.g. production, staging. But can't specify config options per group. I've restructured the config to introduce groups as a top level property allowing you to specify a full config for different groups of URLs. The config is merged with the top level one. This is a breaking change... hence bumping the version number, but is both simpler and more powerful.

@mattheu mattheu merged commit 3b79ba1 into main Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant