Bracken

> @roppa @black-desk maybe I'm misunderstanding your messages, but exactly because objects are unordered, OPs test should pass. The OP's JSON blobs are both arrays, which are ordered, and the...

Related to #944

For me passing in `myMock` rather than `myMock.Mock` does fix this, maybe you missed one? However, you have found a valid bug, [this change](https://github.com/stretchr/testify/commit/b5ce16571001d6e96e1693ac891fed5c2510c651) caused this regression in its attempt...

[testing.M](https://pkg.go.dev/testing#M) has no way of stopping execution, you only have the choice of calling m.Run() or not calling m.Run(). What you are describing is impossible.

You could do that. The assertion would have no need for you to pass it a `testing.M`, there is no `m.Fatal()` method so it's not going to use it for...

I'd be hesitant about adding something as specific as an option to ignore fields in structs beginning with substrings when doing argument matching, there are so many possibilities. Custom matching...

I don't think `Never()` would be very useful, it's almost the same as not defining a call at all. Right now in v1.6.1 `Times(-1)` does not work, it fails expectations...

Parallel tests and subtests are broken in a number of ways with the suite package in the current release. This race, wrong subtest names in failed assertions, cleanup being run...

Dup of #504

In order to test callback functions, you probably want to use `Run()` instead of `MatchedBy()`: ```go m.On("Foo", mock.AnythingOfType("func()")).Run(func(args mock.Arguments){ callback := args.Get(0).(func()) callback() }).Return().Once() ```