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
Update "Using Lighthouse as a trace processor" docs #15790
Comments
It can't be recreated from just the |
It sounds like you may want to save all the artifacts and run the LH audits later? Look at the If you really want to run Lighthouse audits directly, there is this (old) documentation: https://github.com/GoogleChrome/lighthouse/blob/main/docs/hacking-tips.md#using-audit-classes-directly-providing-your-own-artifacts Additionally, you could run Lighthouse with puppeteer directly. Consult our docs for more: https://github.com/GoogleChrome/lighthouse/blob/main/docs/user-flows.md https://github.com/GoogleChrome/lighthouse/blob/main/docs/user-flows.md If you share more about your use case we can provide better advice. |
Thanks for your input.
I'll explain my use case so you can better understand why I'm trying to avoid running lighthouse during the tests phase. We're a large company (hundreds of developers) and we have one team that provides the infrastructure running e2e test for all the devs. This is a custom tests running platform that leverages Given that we are 2 different teams (my team and the team providing the tests infra), I'm trying to be as less invasive as possible. Asking them to integrate lighthouse even as Note that my focus is only performance metrics used to calculate the performance category score as well as That's why I'm currently looking at what's the minimum required I need to gather during the tests phase, so I can send that data to my service running lighthouse, where I can "re-calculate offline" only the required artifacts for the audits I'm interested in and then run lighthouse in Of course I'm not ruling out the possibility that I will eventually have to run lighthouse in |
Summary
I want to leverage my e2e tests written with jest and puppeteer to run lighthouse audits.
When running each test, I'm saving
Trace
andDevtoolsLog
underdefaultPass.trace.json
anddefaultPass.devtoolslog.json
. I'm then trying to run lighthouse as a trace processor like explained in the doc, but it fails due to missingartifacts.json
.So I understand I need to somehow generate the
artifacts.json
fileTrace
andDevToolsLog
only ? I would like to avoid running lighthouse during my e2e testsThanks 🙏
The text was updated successfully, but these errors were encountered: