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
This Issue is meant to begin the discussion around how and if module unit tests can be written to not import the cosmos sdk. This will enable modules to not import the cosmos sdk allowing modules to work with different versions of the cosmos sdk.
Problem Definition
In order to decouple modules from importing the cosmos sdk we need to see if tests can be written in a way to not import some of the cosmos sdk. It is still unclear if this is possible so part of this epic is evaluating the possibility of this working.
Work Breakdown
identify if modules can be written without importing the cosmos sdk
rewrite module test to not import the cosmos sdk
The text was updated successfully, but these errors were encountered:
Summary
This Issue is meant to begin the discussion around how and if module unit tests can be written to not import the cosmos sdk. This will enable modules to not import the cosmos sdk allowing modules to work with different versions of the cosmos sdk.
Problem Definition
In order to decouple modules from importing the cosmos sdk we need to see if tests can be written in a way to not import some of the cosmos sdk. It is still unclear if this is possible so part of this epic is evaluating the possibility of this working.
Work Breakdown
The text was updated successfully, but these errors were encountered: