Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Given that null references cause so much unexpected trouble, what about reporting untested entry points that could cause nil point panics on the code coverage report?
This could be limited to public functions and show as a small flag on the HTML reports.
var projects, err = repo.GetProjects() [nil]
where [nil] would actually be a report flag saying this code wasn't covered with a nil return for this value.
Reference: Null References: The Billion Dollar Mistake
The text was updated successfully, but these errors were encountered:
This is not the purpose of the test coverage tool. If you want to build a tool that does this and use the coverage UI, the code is there for the taking.
Sorry, something went wrong.
No branches or pull requests