You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As long as the keepers are our own we can init them from within, the problem arises when we need cosmos-sdk default keepers, who then have dependencies with their own keepers.
Initting them from scratch would not make sense because it'd be tedious and would require a really careful approach.
Instead we need to rely on the simulation.
So the requirements we need are the following, considering that the domain.Keeper relies on configuration.Keeper and supply.Keeper:
check that an action performed on the domain keeper is allowed by the configuration state in the configuration module (tests are already written in each handler test file (file that ends with _test.go) in domain module and are mapped based on what they're doing and what they're checking so it's easy to understand the purpose).
check that an action performed on the domain keeper is allowed by the supply module ( this is useful to test in case the account has not enough coins to pay fees to process a msg).
We need to implement simulation tests to make sure everything works correctly
Requirements:
The text was updated successfully, but these errors were encountered: