Coveralls vs Go cover

Coveralls analyzes software test coverage, showing teams which code is not covered by tests. Its dashboard presents project coverage percentages and their changes over time, while repository views drill down from a project to sub-projects, files, and individual lines. Build history tracks coverage across branches, including pull requests. Coveralls can add summarized coverage results to pull requests and send status updates that apply coverage criteria to merge decisions. Notifications can go to Slack or webhooks. It supports line and branch coverage, with report formats including LCOV, SimpleCov, Cobertura, JaCoCo, and Clover XML. Coveralls says it works with any CI service and lists more than 30 community-created integrations, a GitHub Action, and a CircleCI Orb. An API can add repositories programmatically and return recent build statistics. Open-source and public repositories are free. The Starter plan is $10 a month for one private repository and includes a 30-day trial. A self-hosted enterprise installation can operate within existing security controls without outbound network access.

Go cover has no write-up on Specifiction yet; its figures are above.