Alternatives to Kobiton logo

Alternatives to Kobiton

Sauce Labs, BrowserStack, BitBar, AWS Device Farm, and Appium are the most popular alternatives and competitors to Kobiton.
24
66
+ 1
0

What is Kobiton and what are its top alternatives?

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.
Kobiton is a tool in the Browser Testing category of a tech stack.

Top Alternatives to Kobiton

  • Sauce Labs
    Sauce Labs

    Cloud-based automated testing platform enables developers and QEs to perform functional, JavaScript unit, and manual tests with Selenium or Appium on web and mobile apps. Videos and screenshots for easy debugging. Secure and CI-ready. ...

  • BrowserStack
    BrowserStack

    BrowserStack is the leading test platform built for developers & QAs to expand test coverage, scale & optimize testing with cross-browser, real device cloud, accessibility, visual testing, test management, and test observability. ...

  • BitBar
    BitBar

    Testdroid provides a set of products for Android and iOS app/game testing on real devices. With different testing solutions, you can efficiently develop and test your mobile apps/games in agile way and achieve your business goals. ...

  • AWS Device Farm
    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. ...

  • Appium
    Appium

    Appium is an open source test automation framework for use with native, hybrid, and mobile web apps. It drives iOS and Android apps using the WebDriver protocol. Appium is sponsored by Sauce Labs and a thriving community of open source developers. ...

  • Experitest
    Experitest

    It allows users to create and run Appium, Selenium, XCUITest & Espresso tests against real devices and web browsers. Users can create & execute hundreds of manual or automated tests in parallel on IOS & Android devices. Users can automate their cross-browser testing, perform visual testing and access advanced analytics. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

Kobiton alternatives & related posts

Sauce Labs logo

Sauce Labs

315
438
Test mobile or web apps instantly across 700+ browser/OS/device platform combinations - without infrastructure setup.
315
438
PROS OF SAUCE LABS
  • 60
    Selenium-compatible
  • 46
    Webdriver compatible
  • 35
    Video recordings of every test
  • 31
    Qa
  • 29
    Mobile support
  • 26
    Any programming language
  • 23
    Developer tools
  • 21
    Test local and firewalled servers
  • 20
    Jenkins integration
  • 18
    Pristine VMs
  • 17
    CI Compatible
  • 11
    Appium support
  • 9
    Parallel testing
  • 8
    Rapid environment preparation
  • 8
    Mobile device support
  • 7
    Easy testing on almost any device
  • 7
    Allows me to Focus more test automation rather than IT
  • 6
    Secure testing and easy setup
  • 5
    Easy setup with CI and fast automated tests
  • 5
    Quick support response
  • 4
    Fast and reliable to host the automated tests
  • 4
    Easy to setup and understand,
  • 3
    Easy setup and integration with Travis Ci
  • 3
    Maintained browser matrix
  • 3
    Easy onboarding, do not need to manager VMs/OS/Browsers
  • 2
    Efficient tool to verify product quality
  • 2
    Teamcity Integration and mobile testing win
  • 2
    Hany for platform testing
  • 2
    Great documentation
  • 2
    Generous free trial
  • 2
    Easy. Straightforward. Scalable
  • 2
    Great way to integrate test suite on cloud
  • 2
    Simplicity of Sauce-connect
  • 1
    Very Good, Quick, flexible Infrastructure Support
  • 1
    It's great for my QA work
  • 1
    Awesome tech support
  • 1
    Having this available for CI servers is fantastic
  • 1
    Amazing service to do cloud cross browser testing
  • 1
    Depth of integrations
  • 1
    Because of its cloud based support for appium
  • 1
    Easy setup, Works great with selenium.
  • 1
    QE support
  • 1
    Manuals are not very well versed for beginners
  • 1
    Secure testing
  • 1
    Cheaper than browserstack
  • 1
    Stable
  • 0
    Simple to set up and integrate so many browser configs
CONS OF SAUCE LABS
  • 2
    Relatively slow
  • 2
    Expensive

related Sauce Labs posts

Shared insights
on
Sauce LabsSauce LabsSeleniumSelenium

I am looking to purchase one of these tools for Mobile testing for my team. It should support Native, hybrid, and responsive app testing. It should also feature debugging, parallel execution, automation testing/easy integration with automation testing tools like Selenium, and the capability to provide availability of devices specifically for us to use at any time with good speed of performing all these activities.

I have already used Perfecto mobile, and Sauce Labs in my other projects before. I want to know how different or better is AWS Device farm in usage and how advantageous it would be for us to use it over other mentioned tools

See more
Zarema Khalilova
Frontend Team Lead at Uploadcare · | 6 upvotes · 296.5K views

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.

See more
BrowserStack logo

BrowserStack

2.7K
533
BrowserStack is the leading test platform built for developers & QAs to expand test coverage, scale, & optimize...
2.7K
533
PROS OF BROWSERSTACK
  • 135
    Multiple browsers
  • 76
    Ease of use
  • 65
    Real browsers
  • 44
    Ability to use it locally
  • 27
    Good price
  • 21
    Great web interface
  • 19
    IE support
  • 17
    Official mobile emulators
  • 15
    Cloud-based access
  • 15
    Instant access
  • 12
    Real mobile devices
  • 8
    Multiple Desktop OS
  • 8
    Selenium compatible
  • 8
    Screenshots
  • 7
    Can be used for Testing and E2E
  • 6
    Pre-installed developer tools
  • 5
    Video of test runs
  • 4
    Supports Manual, Functional and Visual Diff Testing
  • 4
    Favourites
  • 4
    Webdriver compatible
  • 4
    Many browsers
  • 3
    Test Management
  • 3
    Test automation dashboard
  • 3
    Cypress Compatible
  • 3
    Bi-directional Jira Sync
  • 3
    Free for Open Source
  • 3
    Unify and track test cases
  • 3
    Cross-browser testing
  • 2
    Speed is fast
  • 2
    Real devices
  • 1
    Private devices
  • 1
    Test WCAG Compliance
  • 1
    Web accessibility
  • 1
    Visual testing and review
CONS OF BROWSERSTACK
  • 2
    Very limited choice of minor versions

related BrowserStack posts

Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Zarema Khalilova
Frontend Team Lead at Uploadcare · | 6 upvotes · 296.5K views

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.

See more
BitBar logo

BitBar

71
46
Test your mobile apps/games on hundreds of real Android and iOS devices
71
46
PROS OF BITBAR
  • 9
    Best support
  • 8
    The most robust service
  • 7
    Best deployment options (private, public, in-house)
  • 6
    Best coverage of devices globally
  • 4
    Support for all major test automation frameworks
  • 3
    Fantastic API for Apps, Games and Web
  • 3
    Perfect setup for game testing
  • 3
    Image Recognition features
  • 2
    Test Automation Onboarding & Training
  • 1
    Great examples of Java, C#, Python & Ruby test scripts
CONS OF BITBAR
    Be the first to leave a con

    related BitBar posts

    AWS Device Farm logo

    AWS Device Farm

    76
    5
    Test your app on real devices in the AWS Cloud
    76
    5
    PROS OF AWS DEVICE FARM
    • 3
      1000 free minutes
    • 2
      Pay as you go pricing
    CONS OF AWS DEVICE FARM
    • 1
      Records all sessions, blocks on processing when done
    • 1
      You need to remember to turn airplane mode off

    related AWS Device Farm posts

    Appium logo

    Appium

    579
    28
    Automation for iOS and Android Apps
    579
    28
    PROS OF APPIUM
    • 12
      Webdriverio support
    • 6
      Java, C#, Python support
    • 3
      Open source
    • 2
      Great GUI with inspector
    • 2
      Active community
    • 1
      Support android test automation
    • 1
      Internal API access
    • 1
      Support iOS test automation
    CONS OF APPIUM
      Be the first to leave a con

      related Appium posts

      Looking for some advice: we are planning to create a hybrid app for both iOS and Android; this app will consume a REST API. We are looking for a tool for this development with the following attributes:

      • Shallow learning curve; easiness to adopt (all team is new into mobile development, with diverse backgrounds: Java, Python & AngularJS),

      • Easiness to test (we discarded Angular-based tools already: creating a unit test in Angular we considered time-consuming and low value. At this point of the project, we cannot afford UI testing with Selenium/Appium based tools).

      • So far, we are not considering any specific capability of the device. Still, in the mid/long term, we would require the usage of GPS (geolocalization) and accelerometer (not sure if it's possible to use it from a hybrid app). Suggest any other tool if you wish.

      See more
      Kevin Roulleau
      QA Engineer Freelance at happn · | 5 upvotes · 1.2M views

      I chose WebdriverIO and Appium to implement a E2E tests solution on a native mobile app. WebdriverIO goes well beyond just implementing the Selenium / Appium protocol and allows to run tests in parallel out of the box. Appium has the big advantage of supporting iOS and Android platforms, so the test codebase and tools are exactly the same, which greatly reduces the learning curve and implementation time.

      See more
      Experitest logo

      Experitest

      8
      0
      A provider of quality assurance tools for mobile DevOps
      8
      0
      PROS OF EXPERITEST
        Be the first to leave a pro
        CONS OF EXPERITEST
          Be the first to leave a con

          related Experitest posts

          Git logo

          Git

          301.9K
          6.6K
          Fast, scalable, distributed revision control system
          301.9K
          6.6K
          PROS OF GIT
          • 1.4K
            Distributed version control system
          • 1.1K
            Efficient branching and merging
          • 959
            Fast
          • 845
            Open source
          • 726
            Better than svn
          • 368
            Great command-line application
          • 306
            Simple
          • 291
            Free
          • 232
            Easy to use
          • 222
            Does not require server
          • 28
            Distributed
          • 23
            Small & Fast
          • 18
            Feature based workflow
          • 15
            Staging Area
          • 13
            Most wide-spread VSC
          • 11
            Disposable Experimentation
          • 11
            Role-based codelines
          • 7
            Frictionless Context Switching
          • 6
            Data Assurance
          • 5
            Efficient
          • 4
            Just awesome
          • 3
            Easy branching and merging
          • 3
            Github integration
          • 2
            Compatible
          • 2
            Possible to lose history and commits
          • 2
            Flexible
          • 1
            Team Integration
          • 1
            Easy
          • 1
            Light
          • 1
            Fast, scalable, distributed revision control system
          • 1
            Rebase supported natively; reflog; access to plumbing
          • 1
            Flexible, easy, Safe, and fast
          • 1
            CLI is great, but the GUI tools are awesome
          • 1
            It's what you do
          • 0
            Phinx
          CONS OF GIT
          • 16
            Hard to learn
          • 11
            Inconsistent command line interface
          • 9
            Easy to lose uncommitted work
          • 8
            Worst documentation ever possibly made
          • 5
            Awful merge handling
          • 3
            Unexistent preventive security flows
          • 3
            Rebase hell
          • 2
            Ironically even die-hard supporters screw up badly
          • 2
            When --force is disabled, cannot rebase
          • 1
            Doesn't scale for big data

          related Git posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12.4M views

          Our whole DevOps stack consists of the following tools:

          • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
          • Respectively Git as revision control system
          • SourceTree as Git GUI
          • Visual Studio Code as IDE
          • CircleCI for continuous integration (automatize development process)
          • Prettier / TSLint / ESLint as code linter
          • SonarQube as quality gate
          • Docker as container management (incl. Docker Compose for multi-container application management)
          • VirtualBox for operating system simulation tests
          • Kubernetes as cluster management for docker containers
          • Heroku for deploying in test environments
          • nginx as web server (preferably used as facade server in production environment)
          • SSLMate (using OpenSSL) for certificate management
          • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
          • PostgreSQL as preferred database system
          • Redis as preferred in-memory database/store (great for caching)

          The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

          • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
          • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
          • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
          • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
          • Scalability: All-in-one framework for distributed systems.
          • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
          See more
          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 10.4M views

          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.

          See more
          GitHub logo

          GitHub

          292.7K
          10.3K
          Powerful collaboration, review, and code management for open source and private development projects
          292.7K
          10.3K
          PROS OF GITHUB
          • 1.8K
            Open source friendly
          • 1.5K
            Easy source control
          • 1.3K
            Nice UI
          • 1.1K
            Great for team collaboration
          • 868
            Easy setup
          • 504
            Issue tracker
          • 488
            Great community
          • 483
            Remote team collaboration
          • 449
            Great way to share
          • 442
            Pull request and features planning
          • 147
            Just works
          • 132
            Integrated in many tools
          • 122
            Free Public Repos
          • 116
            Github Gists
          • 114
            Github pages
          • 83
            Easy to find repos
          • 62
            Open source
          • 60
            Easy to find projects
          • 60
            It's free
          • 56
            Network effect
          • 49
            Extensive API
          • 43
            Organizations
          • 42
            Branching
          • 34
            Developer Profiles
          • 32
            Git Powered Wikis
          • 30
            Great for collaboration
          • 24
            It's fun
          • 23
            Clean interface and good integrations
          • 22
            Community SDK involvement
          • 20
            Learn from others source code
          • 16
            Because: Git
          • 14
            It integrates directly with Azure
          • 10
            Standard in Open Source collab
          • 10
            Newsfeed
          • 8
            Fast
          • 8
            Beautiful user experience
          • 8
            It integrates directly with Hipchat
          • 7
            Easy to discover new code libraries
          • 6
            It's awesome
          • 6
            Smooth integration
          • 6
            Cloud SCM
          • 6
            Nice API
          • 6
            Graphs
          • 6
            Integrations
          • 5
            Hands down best online Git service available
          • 5
            Reliable
          • 5
            Quick Onboarding
          • 5
            CI Integration
          • 5
            Remarkable uptime
          • 4
            Security options
          • 4
            Loved by developers
          • 4
            Uses GIT
          • 4
            Free HTML hosting
          • 4
            Easy to use and collaborate with others
          • 4
            Version Control
          • 4
            Simple but powerful
          • 4
            Unlimited Public Repos at no cost
          • 3
            Nice to use
          • 3
            IAM
          • 3
            Ci
          • 3
            Easy deployment via SSH
          • 2
            Free private repos
          • 2
            Good tools support
          • 2
            All in one development service
          • 2
            Never dethroned
          • 2
            Easy source control and everything is backed up
          • 2
            Issues tracker
          • 2
            Self Hosted
          • 2
            IAM integration
          • 2
            Very Easy to Use
          • 2
            Easy to use
          • 2
            Leads the copycats
          • 2
            Free HTML hostings
          • 2
            Easy and efficient maintainance of the projects
          • 2
            Beautiful
          • 1
            Dasf
          • 1
            Profound
          CONS OF GITHUB
          • 56
            Owned by micrcosoft
          • 38
            Expensive for lone developers that want private repos
          • 15
            Relatively slow product/feature release cadence
          • 10
            API scoping could be better
          • 9
            Only 3 collaborators for private repos
          • 4
            Limited featureset for issue management
          • 3
            Does not have a graph for showing history like git lens
          • 2
            GitHub Packages does not support SNAPSHOT versions
          • 1
            Expensive
          • 1
            No multilingual interface
          • 1
            Horrible review comments tracking (absence)
          • 1
            Takes a long time to commit

          related GitHub posts

          Johnny Bell

          I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

          I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

          I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

          Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

          Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

          With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

          If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

          See more

          Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

          Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

          Check Out My Architecture: CLICK ME

          Check out the GitHub repo attached

          See more