Need advice about which tool to choose?Ask the StackShare community!
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.
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
BrowserStackStability - Just works. Availability - More than 15 datacenters. Enterprise features like SSO, local testing and SOC2/GDPR compliant.
BitBarBitBar's Dedicated Devices would be a great option for you. It allows you to dedicate (reserve) devices for your use only which also having access to all of the devices in the shared cloud. BitBar has the features and integrations that you are looking for as well.
Pros of BrowserStack
- Multiple browsers130
- Ease of use71
- Real browsers59
- Ability to use it locally40
- Good price23
- Great web interface17
- IE support15
- Official mobile emulators13
- Cloud-based access12
- Instant access11
- Real mobile devices7
- Multiple Desktop OS5
- Screenshots4
- Can be used for Testing and E2E4
- Selenium compatible4
- Pre-installed developer tools3
- Video of test runs3
- Favourites2
- Webdriver compatible2
- Supports Manual, Functional and Visual Diff Testing2
- Many browsers2
- Free for Open Source1
- Cypress Compatible1
Pros of Karma
- Test Runner61
- Open source35
- Continuous Integration27
- Great for running tests22
- Test on Real Devices18
- Backed by google11
- Easy Debugging5
- Remote Control2
Sign up to add or upvote prosMake informed product decisions
Cons of BrowserStack
- Very limited choice of minor versions1
Cons of Karma
- Slow, because tests are run in a real browser1
- Requires the use of hacks to find tests dynamically1
