BrowserStack vs Karma: What are the differences?
BrowserStack: Instant access to a lab of 1000+ real mobile and desktop browsers for testing. Live, Web-Based Browser Testing Instant access to all real mobile and desktop browsers. Say goodbye to your lab of devices and virtual machines; Karma: Spectacular Test Runner for JavaScript. Karma is not a testing framework, nor an assertion library. Karma just launches a HTTP server, and generates the test runner HTML file you probably already know from your favourite testing framework. So for testing purposes you can use pretty much anything you like.
BrowserStack and Karma can be categorized as "Browser Testing" tools.
Some of the features offered by BrowserStack are:
- Real Device Cloud. Test on a range of physical Android and iOS mobile devices and tablets for the most accurate results
- 1100+ desktop browsers. Latest versions of IE, Edge, Safari, Chrome, Firefox and more on a range of Windows and OS X platforms on a robust cloud infrastructure
- Test dev environments. Our Local Testing feature allows you to test development and internal websites seamlessly, without setup or configuration
On the other hand, Karma provides the following key features:
- Test on Real Devices
- Remote Control
- Testing Framework Agnostic
"Multiple browsers" is the primary reason why developers consider BrowserStack over the competitors, whereas "Test Runner" was stated as the key factor in picking Karma.
Karma is an open source tool with 10.7K GitHub stars and 1.61K GitHub forks. Here's a link to Karma's open source repository on GitHub.
According to the StackShare community, BrowserStack has a broader approval, being mentioned in 577 company stacks & 238 developers stacks; compared to Karma, which is listed in 119 company stacks and 57 developer stacks.
What is BrowserStack?
What is Karma?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose BrowserStack?
Why do developers choose Karma?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using BrowserStack?
What are the cons of using Karma?
What companies use BrowserStack?
What companies use Karma?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
BrowserStackIt's incredible how much this service has increased my productivity when it comes to testing new features in multiple browsers. And not only multiple browsers, multiple operating systems as well! And really LOVE that you can run it locally.
BrowserStackWe only really need this for IE support
BrowserStackWe use BrowserStack to run end to end tests with Selenium on our dashboard. It runs automatically before every deployment and cancels it if anything is out of place.
BrowserStackBrowserStack is used by our development and support teams during QA and to try and reproduce bugs.
KarmaAll services, directives and controllers from angular are tested using Karma.
BrowserStackManually and automatically test our web and mobile apps.
KarmaI use Karma as a test runner for javascript unit tests
BrowserStackQA tool to access to all desktop and mobile browsers.
BrowserStackUsed for cross browser scripting especially IE9 :-(
KarmaRun unit and integration tests on real browsers
KarmaRunning Unit tests for Angular UI
KarmaTesting frontend of admin part