limgo
Simple tool to ensure the test coverage does not fall below a limit (by GoTestTools)
goc
A Comprehensive Coverage Testing System for The Go Programming Language (by qiniu)
Our great sponsors
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
limgo
Posts with mentions or reviews of limgo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-08.
-
Code coverage for Go integration tests
A colleague of mine wrote a tool to make this process a bit simpler: https://github.com/gotesttools/limgo
goc
Posts with mentions or reviews of goc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-08.
-
Code coverage for Go integration tests
A few years ago, I used goc to collect coverage from multiple services at the same time when they were used in E2E tests. I was very happy with it. Check it out!
https://github.com/qiniu/goc