What is Testling?

Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.
Testling is a tool in the Continuous Integration category of a tech stack.
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

Who uses Testling?

Companies

Developers
No developer stacks found

Why developers like Testling?

Here’s a list of reasons why companies and developers use Testling
Top Reasons

Testling's 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.
  • Use npm to manage your front-end dependencies.

Testling Alternatives & Comparisons

What are some alternatives to Testling?
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.
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.
Codeship
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.
See all alternatives

Testling's Stats

No Stats