Generate test coverage report #83
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #83 +/- ##
========================================
Coverage ? 59.3%
========================================
Files ? 3
Lines ? 376
Branches ? 0
========================================
Hits ? 223
Misses ? 144
Partials ? 9Continue to review full report at Codecov.
|
chunter0
pushed a commit
to chunter0/hey
that referenced
this pull request
Apr 8, 2024
chunter0
pushed a commit
to chunter0/hey
that referenced
this pull request
Apr 8, 2024
We were not explicitly testing the behavior of some HTTP verb endpoints like /put and /patch, because they currently share an underlying handler with /post which is thoroughly tested. The addition of the /anything endpoint in rakyll#83 made me realize a bit more explicit test coverage would be good, so here we're landing a bit of a refactoring of the test suite to generate tests for all of those endpoints. Along the way, we also improve compatibility with the original httpbin implementation by tricking the stdlib net/http machinery into parsing request bodies for DELETE requests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is kind of a proposal actually. Running a mere coverage check on the main package, I found out it was pretty low and thought it'd be a good idea to have a coverage check run in the CI pipeline.
The script comes from codecov/example-go, and the coverage badge in the readme will work as soon as the account on codecov.io is ready.
Do you also think this make sense?