Raise test coverage to 90% #34
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
mikluko/multiproxy!34
Loading…
Reference in a new issue
No description provided.
Delete branch "test/coverage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Total statement coverage goes from 70.7% on the modernised
mainto 90.4%.The command body moves from
mainintorun, which returns the exit status instead of callingos.Exitthroughzap.Fatal. That lets tests cover-print-ca, startup failures, and serving both listeners. Exit codes are unchanged: 2 for usage, 1 for other failures.The other new tests cover behaviour that had none: log helpers outside the middleware, request IDs and sequence numbers, HTTP handler error mapping and
X-Forwarded-For, MITM with an inner handler that hijacks, CA file errors, and SOCKS reply mapping.CI runs the tests with
-raceand writes total coverage to the job summary. There is no coverage threshold.