test: assert parsed port ranges#15264
Open
immanuwell wants to merge 1 commit into
Open
Conversation
Signed-off-by: Immanuel Tikhonov <122638311+immanuwell@users.noreply.github.com>
immanuwell
force-pushed
the
test-assert-port-range
branch
from
eb44694 to
a70903f
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Tiny test hardening PR.
TestParsePortRangecalledreflect.DeepEqualbut dropped the bool, so the test could go green even when the parsed range was wrong. small but real, imo.Repro on main:
pkg/util/portrange_test.gofrom23-23to24-24go test ./pkg/utilThis makes the test fail on bad parsed ranges and on unexpected errors.
Validation:
go test ./pkg/utilgo test ./pkg/inject ./pkg/utilgo vet ./pkg/util