Need advice about which tool to choose?Ask the StackShare community!
Coveralls vs wercker: What are the differences?
Coveralls: Track your project's code coverage over time, changes to files, and badge your GitHub repo. Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. Free for open source, pro accounts for private repos, instant sign up with GitHub OAuth; wercker: Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Coveralls belongs to "Code Coverage" category of the tech stack, while wercker can be primarily classified under "Continuous Integration".
Some of the features offered by Coveralls are:
- Repository Coverage Statistics
- Individual File Coverage Reports
- Line By Line Coverage
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.
"Free for public repositories" is the top reason why over 44 developers like Coveralls, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
Mapbox, Practo, and Kong are some of the popular companies that use Coveralls, whereas wercker is used by FashionUnited, Hazeorid, and Wantedly. Coveralls has a broader approval, being mentioned in 58 company stacks & 45 developers stacks; compared to wercker, which is listed in 40 company stacks and 23 developer stacks.
My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage
file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage
file from my docker container and get the coverage report with #Codecov.
Pros of Coveralls
- Free for public repositories45
- Code coverage13
- Ease of integration7
- More stable than Codecov2
- Combines coverage from multiple/parallel test runs1
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