Show HN: Chromeless – Headless Chrome Automation on AWS Lambda • Hacker News Board

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#61

Post by smithclay » Thu, Jul 27, 2017, 2:48 AM UTC

gowan wrote: post #53

shamless plug: i've also written a high level api on top of the chrome remote debugger chrominator [1] similar idea. chrominator use promises instead of a fluent api. it also follows the selenium w3c spec where possible. it does cool stuff with evaluate and evaluateAsync where it resolves the remote object to something usable. to be fair there are a few other projects i know about that wrap chrome remote debugger wit…

Shameless plug: I've been hacking on headless chrome in AWS Lambda but with selenium webdriver support [1], also using the binaries from the serverless-chrome [2] project.

To echo another comment on this thread, headless chrome seems well-positioned to shake up the automated browser testing market. The price—especially with the AWS Lambda free tier—is very, very compelling for a number of projects.

[1] https://github.com/smithclay/lambdium [2] https://github.com/adieuadieu/serverless-chrome

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#62

Post by bdcravens » Thu, Jul 27, 2017, 3:21 AM UTC

afandian wrote: post #41

I've got the impression that lots of sites block AWS IP addresses. I wonder if this would hamper the practical use of this on Lambda. I'm doing something similar, and this concern was one motivation for running in our datacentre vs EC2. Does anyone have concrete info on rates of bots blocked from AWS IPs?

In my experience this isn't happening.

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#63

Post by shimon_e » Thu, Jul 27, 2017, 3:31 AM UTC

Another platform that supports headless chrome: https://devexpress.github.io/testcafe/

The error report given by this are some of the best.

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#64

Post by 1024core » Thu, Jul 27, 2017, 4:30 AM UTC

How do cookies work in Chromeless? Can I specify a cookiejar to use? Can I keep cookies separated?

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#65

Post by hackits » Thu, Jul 27, 2017, 4:42 AM UTC

pravda wrote: post #55

extra88 wrote: post #50

Earlier quoted context omitted.

I assume the number one use of this would be test automation for one's own sites so blocking would not be an issue. What are sites' motivations for blocking AWS IPs? I bet there are some reasons I would agree with even though the somewhat crude method of blocking ip range would have some unintended consequences (e.g. blocking people running a personal VPN).

>What are sites' motivations for blocking AWS IPs? I block AWS. So many crawlers up to so much nonsense! I don't block by IP, but by hostname. $block='.amazonaws.com'; $ua = @$_SERVER['HTTP_USER_AGENT']; if (stripos($rh,$block)!==false && stripos($ua,'Silk')===false && stripos($ua,'Safari')===false){ $block_visitor=true; $message="Blocked Host:Amazon Web Services"; }

Just curious what have you seen crawlers do to make you conclude they're up to nonsense?

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#66

Post by penagwin » Thu, Jul 27, 2017, 4:47 AM UTC

bald wrote: post #38

dlisboa wrote: post #23

Earlier quoted context omitted.

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 inst…

Granted that means running ~216 instances per day, or 9 instances per hour (taking 18 minutes per hour to run total). Now you're right, if you're running a screenshot service then this will kill you real fast.

However assuming a 8 hour work day you then get ~27 instances per hour. Each test takes two minutes to run, so for a single user testing, assuming a code - test - code - test routine, you'd be able to do that nearly continuously, for 8 hours a day, every day of the month (no weekends or days off). Seems safe to assume that wouldn't occur.

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#67

Post by ivansavz » Thu, Jul 27, 2017, 5:08 AM UTC

schickling wrote: post #2

I'm really excited to finally open-source Chromeless. We've used NightmareJS and similar tools before to run integration tests but these basically added ~20min to each build. With Chromeless we were able to reduce this time to under a minute! Here is btw a demo playground to try it out: https://chromeless.netlify.com/ Let me know if you have any questions :)

How difficult would it be to also support google cloud functions and the azure offerings? This seems like a really useful standard tool that lots of people might want to use. CI jobs on pull requests that take seconds instead of minutes = big win!

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#68

Post by jpalomaki » Thu, Jul 27, 2017, 6:18 AM UTC

ivansavz wrote: post #67

schickling wrote: post #2

I'm really excited to finally open-source Chromeless. We've used NightmareJS and similar tools before to run integration tests but these basically added ~20min to each build. With Chromeless we were able to reduce this time to under a minute! Here is btw a demo playground to try it out: https://chromeless.netlify.com/ Let me know if you have any questions :)

How difficult would it be to also support google cloud functions and the azure offerings? This seems like a really useful standard tool that lots of people might want to use. CI jobs on pull requests that take seconds instead of minutes = big win!

Azure Container Instances might be good for this: https://azure.microsoft.com/en-us/blog/announcing-azure-cont...

Re: Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

#69

Post by nodesocket » Thu, Jul 27, 2017, 7:27 AM UTC

ivansavz wrote: post #67

schickling wrote: post #2

I'm really excited to finally open-source Chromeless. We've used NightmareJS and similar tools before to run integration tests but these basically added ~20min to each build. With Chromeless we were able to reduce this time to under a minute! Here is btw a demo playground to try it out: https://chromeless.netlify.com/ Let me know if you have any questions :)

How difficult would it be to also support google cloud functions and the azure offerings? This seems like a really useful standard tool that lots of people might want to use. CI jobs on pull requests that take seconds instead of minutes = big win!