fix failure evaluation #8
Merged
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
There were two problems with gdt-kube's evaluation. First, I was
improperly passing a `*interface{}` instead of a `interface{}` to the
`newAssertions()` constructor. This mean the type-casting within
methods like `assertions.lenOK()` was failing.
Secondly, I was not calling `t.Error()` appropriately when there were
failures collected from the assertions.
Signed-off-by: Jay Pipes <jaypipes@gmail.com>
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.
There were two problems with gdt-kube's evaluation. First, I was improperly passing a
*interface{}instead of ainterface{}to thenewAssertions()constructor. This mean the type-casting within methods likeassertions.lenOK()was failing.Secondly, I was not calling
t.Error()appropriately when there were failures collected from the assertions.