Skip to content
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.

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

Implement custom x/mock for customized test environment setup #137

Closed
yoongbok-lee opened this issue Nov 4, 2020 · 2 comments
Closed

Implement custom x/mock for customized test environment setup #137

yoongbok-lee opened this issue Nov 4, 2020 · 2 comments
Assignees

Comments

@yoongbok-lee
Copy link
Collaborator

yoongbok-lee commented Nov 4, 2020

Summary

Currently we initialize all testing environment from scratch, like a new App for example. We should refer to x/mock in the CosmosSDK and unify the initialization process from there.

@hacheigriega hacheigriega reopened this Nov 9, 2020
@hacheigriega hacheigriega self-assigned this Nov 9, 2020
@hacheigriega
Copy link
Contributor

I realized that it gets difficult to avoid import cycles when we use x/mock to test modules that require access to many other modules, like x/shield. Incidentally, I think this is one of the reasons why Cosmos has transitioned to simapp. cosmos/cosmos-sdk#4875

So perhaps we should use simapp as well if we want to do testing of integration of multiple modules?

@yoongbok-lee
Copy link
Collaborator Author

Hmm that makes sense. Let's use simapp. we can transition your branch into a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants