How to pass cookie to lighthouse as part of sitespeed.io
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- docker, javascript
- Domain
- performance, testing
Research direction
Start by reading TestPlans/lhconfig.js and /lighthouse/index.js, then compare their Lighthouse configuration with the Docker command's cookie and emulation options. Reproduce the authenticated run and determine whether the cookie is reaching Lighthouse and whether desktop and network settings are honored.
Written by the indexing model from the issue text.
Description
Hi Team,
I am using docker sitespeed latest Plus 1 docker image to include sitespeed tests and accessibility tests using Lighthouse plugin. Test urls are saved in .txt file and passing cookie for sitespeed.io on command. But for lighthouse i am unable to send cookie from command. I am using below command.
docker run --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io:29.7.0-plus1 TestPlans/APPURLs.txt -n 2 --browsertime.video false --axe.enable --config TestPlans/PageSummaryConfig.json --cookie Jsession=${COOKIE} --plugins.add analysisstorer --plugins.add /lighthouse/index.js --lighthouse.config TestPlans/lhconfig.js ----plugins.remove /gpsi/lib/index.js --outputFolder ./sitespeed-result
Sitespeed results are proper pages. But Cookie is not passing to Lighthouse and page is redirecting to login screen and getting accessibility metrics for that page which is not expected. Also Lighthouse is testing with mobile option. How to do emulation with desktop and network emulation is based on system network.
Could you please help me.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sitespeedio/plugin-lighthouse
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
sitespeedio/plugin-lighthouse#136 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#134 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#133 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#126 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#109 ·
All issues in sitespeedio/plugin-lighthouse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
antfu-collective/icones#398 ·
-
ECmail.com Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wesbos/burner-email-providers#554 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#92 ·