Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Chromeless – Headless Chrome Automation on AWS Lambda

github.com

Post reply on HN
Print view View original

21–30 of 92 posts

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

#21

Post by sorenbs »

schickling wrote: post #18
toomuchtodo wrote: post #13

Earlier 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's of course based on what's more important for you: Running tests non-stop and perfectly utilizing a compute instance vs having the tests executed when you need the results as soon as possible. I might argue that in most cases the latter is what you'd actually want. Especially given that you're getting billed on a millisecond basis.

I would love to have something like this for my scala API tests. We have 3k tests running on 10 ec2 instances and the entire test-suite takes 10 minutes. If some infrastructure would allow me to pay a little more and run all tests in parallel, that would be a game changer for our team.

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

#22

Post by shortj »

toomuchtodo wrote: post #13
shortj wrote: post #4

This would have been awesome to have back when I was heavy in to the UI test automation game. Our best option at that point was a spot instance EC2 fleet and analyzing commits to determine which tests would be the most valuable to run. It's awesome being able to easily run hundreds or thousands of tests in parallel, completely segmented, and pay only on demand. A fantastic use of AWS Lambda! It suddenly becomes reaso…

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.

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

#23

Post by dlisboa »

adieuadieu wrote: post #19
purvis wrote: post #17

Earlier quoted context omitted.

It's parallel because AWS Lambda is inherently parallel? Or are you referring to within JavaScript?

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?

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

#24

Post by schickling »

dlisboa wrote: post #23
adieuadieu wrote: post #19

Earlier 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?

Nope, welcome to the serverless future! :)

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

#25

Post by adieuadieu »

dlisboa wrote: post #23
adieuadieu wrote: post #19

Earlier 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?

Yep. That's one of the main reasons why we're so excited about this project!

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

#26

Post by dlisboa »

schickling wrote: post #24
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?

Nope, welcome to the serverless future! :)

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.

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

#28

Post by schickling »

dlisboa wrote: post #26
schickling wrote: post #24

Earlier quoted context omitted.

Nope, welcome to the serverless future! :)

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

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

#29

Post by languagehacker »

We've been using chrome-remote-interface for test automation in a project that makes heavy use of Lambda for a distributed event processing infrastructure. I'm looking forward to seeing whether we can implement this for running our test automation suite!

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

#30

Post by schickling »

languagehacker wrote: post #29

We've been using chrome-remote-interface for test automation in a project that makes heavy use of Lambda for a distributed event processing infrastructure. I'm looking forward to seeing whether we can implement this for running our test automation suite!

Would love to hear how that goes. Please reach out if you have any problems or questions. The easiest way is to ping me on Slack: https://slack.graph.cool
Post reply on HN