GOMODULES
/
testify
mirror of https://github.com/stretchr/testify.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document consequences of calling t.FailNow() 

These comments are adapted from t.FailNow()'s own documentation.

Closes #1701
pull/1710/head
Grégoire Paris 2025-03-19 20:48:34 +01:00
parent f784abc221
commit 89086b0757
No known key found for this signature in database
GPG Key ID: 24D48B8012B116BF
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
mock/mock.go
View File

@ -332,6 +332,8 @@ func (m *Mock) TestData() objx.Map {
*/ */
// Test sets the test struct variable of the mock object // Test sets the test struct variable of the mock object
// Test should not be called on an object that is going to be used in a
// goroutine other than the one running the test function.
func (m *Mock) Test(t TestingT) { func (m *Mock) Test(t TestingT) {
m.mutex.Lock() m.mutex.Lock()
defer m.mutex.Unlock() defer m.mutex.Unlock()

2
require/doc.go
View File

@ -23,6 +23,8 @@
// //
// The `require` package have same global functions as in the `assert` package, // The `require` package have same global functions as in the `assert` package,
// but instead of returning a boolean result they call `t.FailNow()`. // but instead of returning a boolean result they call `t.FailNow()`.
// A consequence of this is that it must be called from the goroutine running
// the test function, not from other goroutines created during the test.
// //
// Every assertion function also takes an optional string message as the final argument, // Every assertion function also takes an optional string message as the final argument,
// allowing custom error messages to be appended to the message the assertion method outputs. // allowing custom error messages to be appended to the message the assertion method outputs.