Mechanism for assertions to signal immediate/fatal termination of failed test cases #33
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.
...via
*testing.T.Fatalf
.This change is meant to be released in concert with smarty/assertions#55, which introduces a new
must
package.This new feature addresses cases where an assertion failure early in a test should kill a test immediately. Here are a few examples of how we've approached this up until this PR:
Length checks before assertions:
Old way:
New way:
Error checking before subsequent assertions:
Old way:
New way: