Skip to content

Warn against usage inside a gouroutine #952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
greg0ire wants to merge 1 commit into
base: v2
Choose a base branch
from
Open

Warn against usage inside a gouroutine #952

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,14 @@ Why use mockery over gomock?
4. mockery's CLI is more robust, user-friendly, and provides many more options
5. mockery supports generics (this may no longer be an advantage if/when gomock supports generics)

Warning about goroutine safety
------------------------------

As mentioned earlier, mockery relies on `testify`, which comes with a limitation:
calling an unexpected method on a mock object can cause necessary cleanups such
as channel closing to be skipped. This means that ideally, mock objects should
only ever be used from the same goroutine that runs the test function.

Who uses mockery?
------------------

Expand Down