Ask HN: Is it worth releasing another open-source test coverage aggregator?

2 points by mmarian ↗ HN
Sonarqube is a hassle to self-host. Codecov requires a license that limits you to 50 users. There are a few no-strings-attached projects (OpenCov, Covergates) but they’re deprecated. Am I missing out any other options?

If not, I’m wondering if it’s worth releasing one; written in Go so it’s easy to run. Would people actually adopt it, even if it’s a bare-bones project that, say, only works for one or two languages (Python & JS)? I’m worried it’s not something teams care about, since they just default to a paid service that has more features.

1 comment

[ 2.8 ms ] story [ 11.6 ms ] thread
Is the goal to build something and learn something from the experience, or try and build something with adoption in mind?

If the former, the answer to your question is always "yes": if there's something to learn and you're interested in that problem space, it's always worthwhile.

If you're looking at the latter, you're essentially building a product. The next question should then be "is there part of what's out there that you're confident you can do differently/better?"