I'm investigating the possibility of using a container called Spoonium (https://spoon.net/docs/sandboxes/selenium-sandbox). It claims to run your selenium scripts in their containers against various browsers/versions by taking the place of your Selenium Grid (or acts as a substitute grid...however you want to look at it). Has anyone worked with Spoonium? I've searched the forum and haven't found anything even referencing Spoonium.
I'm just wondering what experiences others have had with this product.
I've tried it as a trial, but never rolled it out to any organization yet.
My personal thoughts on Spoonium is, I feel its cool there is an alternative to Sauce and Browserstack. I like the cost, but at this point, I see it more as a hobbyist at this point.
What I like about it:
* Pricing looks nice, one of the biggest complaints I get when writing a business proposal for Sauce Enterprise is, why pay $18k/month for a 20 concurrent VM setup when I can easily buy a top of the line blade server for less than $10k. It's always a pain in the *** having to put numbers
* The solution looks pretty simple, I don't have to manage OS updates, Selenium updates, and browser updates because they manage a library of prebaked images.
What I'm apprehensive about are:
* I feel that a big part of the infrastructure management will have to be done by the QA team. Being that they are containers you're running on inhouse machines, that becomes an infrastructure you have to manage yourself. At that point, I'd probably lean towards using an open source solution that uses popular open source platform such as Docker, https://github.com/SeleniumHQ/docker-selenium
* Infrastructure integration is easiest with Sauce IMO, the sauce connect makes setting up temporary tunnels as part of a CI process a breeze. They have Jenkins plugins (and many other CI build managers as well). BrowserStack IMO is a bit harder to setup, but is a simple Java executable that setups a tunnel quite easily. The key here is they have machines running and ready to go, just setting up a tunnel is what you need. I rather not have spinning up VMs when I'm trying to optimize a sub 5 minute build process.
* A good portion of BrowserStack and SauceLabs values are their value added tools. The Selenium over the wire logging and screen recording make it easier to debug issues and attach recordings to bugs.
* Reliability and response. I couldn't find any white papers of scaled up usage of their platform. Up-time/downtime is very important to me, I estimate about $195 of QA/DEV time is loss per every 6 person Agile team for every hour of downtime, with about an additional $3900 of economic value lost per team. That figure is more than tripled if this at a crucial period such as during a release.
Thank you for your input! I shall continue my research.
One of the teams in our organization has a fully implemented Selenium Grid that they've been using for a few years. I'm working with the team lead and she and I are going to investigate Spoonium a little deeper and see what we find. I'll post our results when we finish our testing. We're not throwing a bunch of time at it since it's just a proof of concept so it will not be fully vetted but we will have some initial findings that might prove helpful to others.
Again, thanks for your thoughts. They are helpful!
Tags for this Thread