Appveyor vs Karma

Appveyor vs Karma: What are the differences?

Appveyor: Continuous Integration and Deployment service for busy Windows developers. AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server; 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.

Appveyor can be classified as a tool in the "Continuous Integration" category, while Karma is grouped under "Browser Testing".

Some of the features offered by Appveyor are:

• Scriptless, repetitive, one-click deployment of build artifacts to multiple environments
• YAML configuration
• Backed by Windows Azure platform

On the other hand, Karma provides the following key features:

• Test on Real Devices
• Remote Control
• Testing Framework Agnostic

"Github integration" is the top reason why over 18 developers like Appveyor, while over 56 developers mention "Test Runner" as the leading cause for choosing 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, Karma has a broader approval, being mentioned in 119 company stacks & 57 developers stacks; compared to Appveyor, which is listed in 19 company stacks and 16 developer stacks.