Need advice about which tool to choose?Ask the StackShare community!
Add tool
Appveyor vs Testling: 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; Testling: Automatic browser tests on every push. Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.
Appveyor and Testling belong to "Continuous Integration" category of the tech stack.
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, Testling provides the following key features:
- Write tests with a minimal test api that works in both node and browsers.
- Run your tests in node and your local browsers.
- Run tests in mocha for qunit, tdd, bdd, and exports-style tests.
Testling is an open source tool with 337 GitHub stars and 47 GitHub forks. Here's a link to Testling's open source repository on GitHub.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of Appveyor
Pros of Testling
Pros of Appveyor
- Github integration20
- Simple, reliable & powerful18
- Hosted12
- YML-based configuration11
- Nuget support10
- Windows support6
- Free for open source4
- Automatic deployment4
- Great product, responsive people, free for open-source3
- Easy PowerShell support2
- Easy handling of secret keys2
- Remote Desktop into Build Worker1
- Advanced build workers available1
Pros of Testling
- Quality2
Sign up to add or upvote prosMake informed product decisions
Cons of Appveyor
Cons of Testling
Cons of Appveyor
- Complex user interface1
- Poor documentation1
Cons of Testling
Be the first to leave a con
Sign up to add or upvote consMake informed product decisions
No Stats
What is Appveyor?
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.
What is Testling?
Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.
Need advice about which tool to choose?Ask the StackShare community!
Jobs that mention Appveyor and Testling as a desired skillset
What companies use Appveyor?
What companies use Testling?
What companies use Appveyor?
See which teams inside your own company are using Appveyor or Testling.
Sign up for StackShare EnterpriseLearn MoreSign up to get full access to all the companiesMake informed product decisions
What tools integrate with Appveyor?
What tools integrate with Testling?
What tools integrate with Appveyor?
What tools integrate with Testling?
No integrations found
Sign up to get full access to all the tool integrationsMake informed product decisions
What are some alternatives to Appveyor and Testling?
TeamCity
TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Jenkins
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.
CircleCI
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.