CBG-4455 do not panic when calling FailNow
#7308
Merged
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.
CBG-4455 do not panic when calling
FailNow
Confusingly, require.FailNow's signature is
FailNow(t TestingT, failureMessage string, msgAndArgs ...interface{})
. There are a few consequences to this, one of which is that expectingfailureMessage
to be formatted will not happen. The second problem is if the first argument inmsgAndArgs
is not a format string, then the test harness can panic.rules-*.go
files so the test files in that directory aren't picked up.Integration Tests
GSI=true,xattrs=true
https://jenkins.sgwdev.com/job/SyncGateway-Integration/2898/ (known, unrelated failure)