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

Coveralls

1.6K
277
+ 1
68
wercker

395
157
+ 1
242
Add tool

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.

Decisions about Coveralls and wercker

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Coveralls
Pros of wercker
  • 45
    Free for public repositories
  • 13
    Code coverage
  • 7
    Ease of integration
  • 2
    More stable than Codecov
  • 1
    Combines coverage from multiple/parallel test runs
  • 35
    Automatic Deployments
  • 33
    Free
  • 25
    Easy config via yaml
  • 23
    Awesome UI
  • 23
    Github integration
  • 22
    Continuous Deployment
  • 16
    Supports both Github and Bitbucket
  • 14
    Easy to setup
  • 12
    Reliable
  • 11
    Bitbucket Integration
  • 4
    Community-driven components (boxes and steps)
  • 4
    Fast builds
  • 4
    Easy to get started
  • 4
    Docker based
  • 3
    Easy UI
  • 3
    Flexible configuration via YAML
  • 2
    Multi-target deploys
  • 1
    Trigger by branch name
  • 1
    Great UI, free and an active Slack channel :)
  • 1
    Docker support
  • 1
    Multiple configurable build steps

Sign up to add or upvote prosMake informed product decisions

What is Coveralls?

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.

What is wercker?

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

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

What companies use Coveralls?
What companies use wercker?
See which teams inside your own company are using Coveralls or wercker.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Coveralls?
What tools integrate with wercker?

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

What are some alternatives to Coveralls and wercker?
Jumpsuit
A powerful and efficient Javascript framework that helps you build great apps. It is the fastest way to write scalable React/Redux with the least overhead.
Codecov
Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
SonarQube
SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
Istanbul
It is a JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.
uberalls
Code coverage metric storage service. Provide coverage metrics on differentials with Phabricator and Jenkins, just like Coveralls does for GitHub and TravisCI.
See all alternatives