Need advice about which tool to choose?Ask the StackShare community!

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; wercker:Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Testling and wercker can be primarily classified as "Continuous Integration" tools.

Some of the features offered by Testling are:

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.

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

Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.

Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.

Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.

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.

No Stats

- No public GitHub repository available -

What is Testling?

Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.

What is wercker?

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

What tools integrate with Testling?

What tools integrate with wercker?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Testling and wercker?

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.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

GitLab CI

GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.