🌱 Enhance test output and management in ValidateTestReturn #3810
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.
What kind of change does this PR introduce?
test helper enhancement
What is the current behavior?
t.Fail()
,t.Errorf
, or similar) is done by all the callersWhat is the new behavior (if this is a feature change)?**
ValidateTestReturn
.t.Log
is used to print the details seen by the test. These details are only shown when a test fails, or-v
is passed (like the e2e tests).Which issue(s) this PR fixes
Special notes for your reviewer
You'll see three sort of changes:
ValidateTestReturn
handles it:Should(BeTrue())
part relates to1.
above)ValidateTestReturn
that let it all happen.Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)