11–20 of 92 posts
Can I use this somehow in a container? Farm out headless chrome + selenium on a local data center? I would be grateful for any hints.
So to clarify - this is basically a Node.JS wrapper around Chrome headless, right? =_) Seems pretty awesome. My use case is to take screenshots of various pages - the docs don't mention the default viewport dimensions, btw.
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…
The first two examples seem to return 404, for me:
So to clarify - this is basically a Node.JS wrapper around Chrome headless, right? =_) Seems pretty awesome. My use case is to take screenshots of various pages - the docs don't mention the default viewport dimensions, btw.
One minor housekeeping comment: The first two examples seem to return 404, for me: https://github.com/graphcool/chromeless#examples
So to clarify - this is basically a Node.JS wrapper around Chrome headless, right? =_) Seems pretty awesome. My use case is to take screenshots of various pages - the docs don't mention the default viewport dimensions, btw.
Yes exactly + this can run (in parallel) on AWS Lambda, so you don't need to worry about provisioning & running servers. That's actually the part I'm most excited about :)
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.
Earlier quoted context omitted.
Yes exactly + this can run (in parallel) on AWS Lambda, so you don't need to worry about provisioning & running servers. That's actually the part I'm most excited about :)
It's parallel because AWS Lambda is inherently parallel? Or are you referring to within JavaScript?
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.