What is Sauce Labs and what are its top alternatives?
Top Alternatives to Sauce Labs
TestingBot provides automated and Manual cross browser testing in the cloud. Make sure your website looks ok in all browsers. ...
Live, Web-Based Browser Testing Instant access to all real mobile and desktop browsers. Say goodbye to your lab of devices and virtual machines. ...
It's implemented to ensure a website's functionality and design and includes testing a range of devices and operating systems being used in the market and customer base. ...
Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well. ...
It enables developers and testers to perform automated and manual testing of mobile apps and websites on real devices. Modern DevOps and Quality environments require apps to be tested on hundreds of device/OS/browser combinations. Managing an in-house device-lab is expensive, resource intensive, restrictive and very manual. Kobiton allows for instant provisioning of real devices for testing with automated or manual scripts, and also allows current on-premise devices to be plugged in to form a holistic testing cloud. ...
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project. ...
A cloud-based automated cross browser testing platform. LambdaTest allows you to perform automation testing on a scalable, secure, and reliable Selenium Grid online. It provides access to the network of 2000+ real browsers and OSes. ...
AWS Device Farm
Run tests across a large selection of physical devices in parallel from various manufacturers with varying hardware, OS versions and form factors. ...
Sauce Labs alternatives & related posts
- Good price5
- Jenkins integration2
- Real Devices2
- Mobile support2
- Stable Tests1
- Great customer support1
- IE support1
- Webdriver compatible1
- Bamboo Integration1
- TeamCity Integration1
- Parallel Testing1
- Highly Available1
related TestingBot posts
- Multiple browsers127
- Ease of use69
- Real browsers58
- Ability to use it locally40
- Good price22
- Great web interface17
- IE support15
- Official mobile emulators13
- Cloud-based access12
- Instant access11
- Real mobile devices6
- Multiple Desktop OS5
- Can be used for Testing and E2E4
- Selenium compatible4
- Video of test runs3
- Pre-installed developer tools3
- Many browsers2
- Webdriver compatible2
- Supports Manual, Functional and Visual Diff Testing2
- Free for Open Source1
- Cypress Compatible1
- Very limited choice of minor versions1
related BrowserStack posts
I am working on #OpenSource file uploader. The uploader is the widget that other developers embed in their apps. It should work well in different browsers and on different devices. BrowserStack and Sauce Labs help to achieve that. I can test the uploader in many varieties of browsers+OS only used my browser without virtual machines.
related CrossBrowserTesting posts
- Automates browsers165
- Essential tool for running test automation100
- Remote Control24
- Supports end to end testing7
- Data crawling7
- Functional testing6
- Easy set up5
- End to End Testing3
- Easy to integrate with build tools3
- Record and playback2
- Easy to scale2
- Compatible with Python2
- The Most flexible monitoring system2
- Integration Tests2
- Comparing the performance selenium is faster than jasm2
- Integrated into Selenium-Jupiter framework0
- Flaky tests3
- Slow as needs to make browser (even with no gui)1
related Selenium posts
With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.
related Kobiton posts
- Hosted internally520
- Free open source463
- Great to build, deploy or launch anything async313
- Tons of integrations243
- Rich set of plugins with good documentation208
- Has support for build pipelines108
- Open source and tons of integrations71
- Easy setup63
- It is open-source61
- Workflow plugin54
- Configuration as code11
- Very powerful tool10
- Many Plugins9
- Git and Maven integration is better8
- Great flexibility8
- Continuous Integration6
- Slack Integration (plugin)6
- Github integration6
- Easy customisation5
- Self-hosted GitLab Integration (plugin)5
- 100% free and open source4
- Docker support4
- Excellent docker integration3
- Fast builds3
- Platform idnependency3
- Pipeline API2
- Can be run as a Docker container2
- It`w worked2
- Hosted Externally2
- AWS Integration2
- It's Everywhere2
- NodeJS Support1
- PHP Support1
- Ruby/Rails Support1
- Universal controller1
- Easily extendable with seamless integration1
- Build PR Branch Only1
- Workarounds needed for basic requirements12
- Groovy with cumbersome syntax7
- Plugins compatibility issues6
- Limited abilities with declarative pipelines6
- Lack of support5
- No YAML syntax4
- Too tied to plugins versions2
related Jenkins posts
Releasing new versions of our services is done by Travis CI. Travis first runs our test suite. Once it passes, it publishes a new release binary to GitHub.
Common tasks such as installing dependencies for the Go project, or building a binary are automated using plain old Makefiles. (We know, crazy old school, right?) Our binaries are compressed using UPX.
Travis has come a long way over the past years. I used to prefer Jenkins in some cases since it was easier to debug broken builds. With the addition of the aptly named “debug build” button, Travis is now the clear winner. It’s easy to use and free for open source, with no need to maintain anything.
Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).
It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear
vagrant up or
vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.
I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as
vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.
We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.
If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.
The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).
Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.
- Pocket friendly pricing11
- Integration with Gitlab10
- Good Performance10
- Integration with Bitbucket10
- Integration with Jira9
- Great support9
- Integration with GitHub9
- Integration with Trello9
- Integration with Slack9
- Integration with Asana9
- Cross browser testing9
- Clean UI and Easy to use8
- Integration with Hive7
- IE and Edge support7
- Pre-installed developer tools7
- Local app testing5
- Integration with VSTS4
- Integration with Teamwork4
- Multiple Browsers4
- Real time testing feature is flawless3
- Faster Speed2
- Selenium automation2
- Up-to-date Browser collection2
- Robust Selenium Grid1
- 24/7 Customer Chat Support1
related LambdaTest posts
- 1000 free minutes3
- Pay as you go pricing2
- Records all sessions, blocks on processing when done1
- You need to remember to turn airplane mode off1