GoogleChromeLabs / GoogleChromeLabs/chrome-for-testing
Installation Instructions
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 159
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 3
Description
Could some basic installation documentation be provided to show users how to make use of the provided binaries?
The [blog page](https://developer.chrome.com/blog/chrome-for-testing/) demonstrates the use of the `@puppeteer/browsers` package to install the binaries, but this isn't possible in all environments. And this repo doesn't mention anything about installation.
I appreciate that it's complex to provide detailed instructions for every platform and use-case, but even some simple guidelines would be helpful. eg. "Download these, unzip to , mark as executable...".
I've managed to get everything working in a Debian-based container, but I'm not sure if I'm doing it right at all. For example, it appears that I also need to install the main Debian chrome package to install various dependencies the Chrome for Testing binary needs. I'm not sure if this is expected or not.
Anyway, thanks for working on this! The APIs and binaries work well, just a thought on user-experience.
Contributor guide
Research direction
Start by reviewing the repository's existing documentation and the linked Chrome for Testing blog guidance, then compare it with the @puppeteer/browsers installation approach. Document basic binary download, extraction, executable permissions, and dependency expectations, including the Debian-based container case, with clear limits for platform-specific guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100