I've been super excited about Chrome headless but haven't had a chance to dig into using it yet. The api here looks amazing for getting started without getting lost in the weeds. It'd be fairly trivial to hook this up to a Slackbot and to get on-demand screenshots of various pages on my websites, etc.
Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
31–40 of 92 posts
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#32I've been using serverless-chrome for the past few weeks and this looks like a big improvement in usability!
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#33I've been using serverless-chrome for the past few weeks and this looks like a big improvement in usability! https://github.com/adieuadieu/serverless-chrome
Chromeless is actually built on top serverless-chrome and was developed together with the author of serverless-chrome :)
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#34Earlier quoted context omitted.
Do the math. If you're suggesting running all the tests , drastically increasing your compute volume, it's probably cheaper to use a dedicated instance running at max CPU utilization.
It absolutely depends on how burst driven your utilization pattern is, but don't forget the cost to actually manage the test cluster, and the engineering cycles that go into optimizing and sharding those tests across the cluster.
For sure, lots of considerations to take into account. If you're already running your own CI pipeline though, tests on top of it are trivial (in my experience running a Jenkins CI pipeline for a python monolith). Tweak your test runner, upsize the EC2 instance, and go grab a mojito.
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#35Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#36The last time I tried headless Chrome, file downloads were a PITA. Has anyone tried downloads with Chromeless?
Other than taking a screenshot and evaluating JS code in the context of Chrome and returning JSON, we haven't yet implemented any file-download features. But it might be possible for us to implement something. Would you mind creating an issue here describing your use case so we can discuss it further? https://github.com/graphcool/chromeless/issues/new
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#37Earlier quoted context omitted.
You guys should put up an example on how to convert a (small) test suit to use it, like you said you did in your top comment. The examples you have are cool but don't really help visualize that parallelism gain.
Sounds like a great idea. Would you mind creating an issue here so we can track this? https://github.com/graphcool/chromeless/issues
Done.
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#38Earlier quoted context omitted.
Parallel in that you can invoke many Lambda functions at the same time and have them run independently of each other
So basically if I had 200 automations I could run them on 200 lambdas and have them finish by the time the slowest one finishes? That pretty awesome, specially for testing. For many cases this would also fall under the free tier since it not that many requests/usage...it kinda seems too good to be true. Am I missing something?
> For many cases this would also fall under the free tier since it not that many requests/usage...it kinda seems too good to be true
(since I've ran into the same trap a couple of weeks ago and ended up with USD 650 of unanticipated charges): the free Lambda tier includes
* 1M requests
* 400k GB-seconds
--> the GBsec can be a serious bottleneck. Imagine you're running each Lambda instance with 512MB RAM and each instance takes 2 mins to complete your test. This means that one Lambda instance is ~61.5 GBsec, meaning you can execute ~6,500 of these instances per month to remain in the free tier.
Depending on how extensive your tests are/how often you run them, you might run out of free GBsec well before you'd run out of the requests quota.
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#39@schickling - When will the PDF support arrive?
https://github.com/graphcool/chromeless/blob/master/docs/api...
Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda
#40Cool. Now can you use it with webdriver functions instead of re-inventing the API?