CoverItUp

CoverItUp - is a new, one of its kind, complete solution for software engineers to measure code metrics.

This tool empowers developers to take control of their code coverage analysis for any type of matrices, all in one place.

This tool is fully customizable tool to track metrics that should matter to you the most. Such as, not just the code coverage, but equally important other metrics. Such as, build times, number of dependencies, bundle sizes etc. Together with additional features, which I share further in this post.

Context:

Mostly all repos use services like CodeCov, Coveralls badges to display the code-coverage of unit tests on their README on Github. Over years, many other badges, such as, number of downloads, number of people online on Discord etc also made their way into the README.

However, there are other indicators that are equally important. And developers have less control as developers are mostly restricted to the tools that are available right now to record those metrics.

Therefore, I designed this tool in such a way, that developers can record any types of scores that they see fit.

Generally for any software project, we use tools like SonarQube for code inspection, CodeCov for code coverage, Code Climate for smells and others.

For enterprise users, this also means expensive licenses and managing several self-hosting. Therefore, some may consider it as a free alternative to CodeCov or SonarQube.

And for users, using the cloud services for these respective tools, involves managing separate accounts, authentications etc.

All these tools provide solutions to one or two metrics. Hence, users end up using multiple services for different use cases in the same project.

We didn’t want to do either. Instead, provide full control to developer with the choice of indicator a developer wants to measure.

Over my years of development, I have realized that just badges may not be enough to determine the trajectory of a repository. Therefore, I implemented trend charts that can be embedded inside the README as images, the same way we embed badges.

On top of the core feature to track code wellness, the tool provides badges and charts that can be embedded into the README. It also provides smart feedback to users on pull requests by sharing the difference in the indicators for 2 branches. The tool doesn’t spam the comment box, and upon new commits filters out the diff that have already been commented.

It comes in dark and light themes. The embedding of charts comes in 2 different themes. The width and heights are fully adjustable and output can be either png or svg if you prefer smaller sizes. SVG are best suited to embed in the README or pull request comments. While PNG are used if you want to create your own dashboards on a Wiki or Confluence page for all the repositories in an organization.