Ryo Shibayama discusses using chromeless to run browser integration tests and take screenshots on AWS Lambda in parallel. Chromeless can run tests remotely on Lambda functions deployed through its proxy service. Issues may arise from missing fonts, but these can potentially be resolved by modifying serverless-chrome or waiting for font configuration support. Running tests explosively in parallel on Lambda is an interesting approach to scale testing.
6. chromeless
Runs locally or headless on AWS Lambda
It can be used to
Run 1000s of browser integration tests in parallel
Crawl the web & automate screenshots
Write bots that require a real browser
https://github.com/graphcool/chromeless
8. Setup ow
1. Clone chromeless repo, npm install in proxy
service directory
2. Con gure AWS's access key and secret
3. Deploy to own infrastructure with dedicated
command( npm run deploy )
4. Request to the proxy using issued endpoint, API
key
Notice: Use the same region between AWS
services chromeless uses
14. Why □?
chromeless depends on severless-chrome
By default, some fonts are not installed in
serverless-chrome
#49 Include Chinese/Japanese/Korean/more
fonts in headless Chrome binary
16. Missing fonts...
But we can resolve this issue to re-archive
serverless-chrome with fontcon g bundled
My former senior was writing a blog about this
issue
17. Hmm
It's better to wait for serverless-chrome supports
multi fonts con guration
Because chromeless depends on it...
If we use serverless-chrome as standalone, I think
we should install and use our own fonts
18. Conclusion
The approach of explosively increasing the
number of parallels using Lambda is very
interesting
Keep watching these repos
More in details on my blog serima.co/blog
19. Bonus
PhantomJS: Stepping down as maintainer
https://news.ycombinator.com/item?
id=14105489
We should choose headless chrome as an e2e test
tool from now on