We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
testutil/keeper.FungibleKeeper
Part of #878
Fungible test keeper currently use empty instances for dependences
bankkeeper := bankkeeper2.BaseKeeper{} authkeeper := authkeeper2.AccountKeeper{} evmKeeper := evmkeeper.Keeper{}
which makes it not usable for most unit tests. The ideal model for unit tests would be to use mocking for the dependent modules.
Example using Mockery https://github.com/vektra/mockery
mockery
mocks
testutil/ keeper/ fungiblemocks/ bank.go auth.go evm.go
Returns the mocks along with the test keeper in FungibleKeeper
FungibleKeeper
func FungibleKeeper(t testing.TB) ( *keeper.Keeper, fungiblemocks.BankKeeperMock, fungiblemocks.AccountKeeperMock, fungiblemocks.EVMKeeperMock, sdk.Context, )
The text was updated successfully, but these errors were encountered:
testutil
lumtis
Successfully merging a pull request may close this issue.
Part of #878
Fungible test keeper currently use empty instances for dependences
which makes it not usable for most unit tests. The ideal model for unit tests would be to use mocking for the dependent modules.
Example using Mockery https://github.com/vektra/mockery
mockery
commands to generate the module mocks undermocks
Returns the mocks along with the test keeper in
FungibleKeeper
The text was updated successfully, but these errors were encountered: