testify
testify copied to clipboard
stretchr
A toolkit with common assertions and mocks that plays nicely with the standard library
## Summary fix typos in documentation, comments and tests ## Motivation I looked at the documentation, then found one typo in Panic: "functon" instead of "function" So decided to check...
The the moment once cannot express negative expectations via `.On()`. Instead, you must use `.AssertNotCalled`. It would be useful if negative expectations could be expressed something like `.On().Never()`. Note that...
## Summary Add opportunity to setup or teardown each subtest ## Changes * Added method to the Suite struct that allows to save parent suite (with it's methods) and execute...
## Summary Added ability to run tests multiple times with a single SetupSuite and TearDownSuite ## Changes Running go test now accepts flag testify.c which defines how many times we...
FailfastSuite used a callOrder slice that gets populated by the suite methods and compared it to a string literal. When test.count is > 1 callOrder is overpopulated and does not...
Assume that a function that we're mocking accepts a `slice[]` of `strings`, and it returns a response `friendData` thereafter. A typical mock for this would be something like below -...
I have a test suite In the `SetupSuite` method I wait for some event to happen. If it doesn't happen within a certain timeout, I call `t.FailNow()` The problem is...
I'm writing a testing suite that spins up some resource on `SetupSuite` (in my case a virtual machine), runs some tests against it, then destroys the resource on `TearDownSuite`. Now,...
FORTIFY is throwing vulnerability with Yaml V2, can you please migrate to V3
`go get` resulted in undefined errors on my machine. Once I updated my Go version to 1.19 I got this handy message: 'go get' is no longer supported outside a...
