Coveralls vs wercker

Overview

Coveralls

Stacks1.7K

Followers278

Votes68

wercker

Stacks392

Followers156

Votes242

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.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Coveralls, wercker

Felipe

May 24, 2020

Needs advice

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.

198k views198k

Comments

Detailed Comparison

Coveralls	wercker
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 is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Repository Coverage Statistics;Individual File Coverage Reports;Line By Line Coverage;Repository Overview	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.; Security - We manage the nodes and schedulers, and run your jobs utilising a network isolated approach; we take care of all security patches and updates.; Deploy - Wercker is customisable and integrates with a variety of deploy targets and supports registries.
Statistics
Stacks 1.7K	Stacks 392
Followers 278	Followers 156
Votes 68	Votes 242
Pros & Cons
Pros 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	Pros 35 Automatic Deployments 33 Free 25 Easy config via yaml 23 Github integration 23 Awesome UI
Integrations
Travis CI CircleCI Semaphore Jenkins Codeship	Bitbucket GitHub Red Hat OpenShift Heroku Docker

What are some alternatives to Coveralls, 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

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.

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.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Codecov

Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.

Related Comparisons

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.

Coveralls vs wercker