Need advice about which tool to choose?Ask the StackShare community!
Testling vs wercker: What are the differences?
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.
We migrated all our CI/CD pipelines to CircleCI back in 2017 and are particularly happy about it since!
Our top loved feature is unlimited parallelism. We can run as many builds concurrently as we want.
We also use orbs, pipeline parameters, reusable commands, build cache, test insights.
For some of the heavier repos, we use a larger resource class and mount RAMdisk to a file system to speed up builds.
Pros of Testling
- Quality2
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1
