Refactor multilib::wasm::WasmKeeper tests to use mulitest::wasm::Wasm instead of internal functions
#3
Assignees
Labels
enhancement
New feature or request
Comments
This was referenced Sep 13, 2021
|
I think we can depend on WamsKeeper, as we have generic in App/Router and do call them sometimes. I do agree we can avoid calling private methods and try only pub ones. Any way to get the compiler to enforce that? |
|
Also find this as not urgent... but a nice cleanup |
|
Closed - over 2 years refactoring task, even if still reasonable it should be reconsidered from scratch |
Kayanski
referenced
this issue
in AbstractSDK/cw-multi-test-fork
Jun 27, 2024
* Integrated rust contracts * Some clippy fixes ? * Less unsafe code * Fixed with features * Added dual storage for cosmwas-std * Added dual storage for wrappers as well * Added storage and querier inside rust code contracts * Modified storage accessor to just wrap * Fixed contract address when querying contract * Fixed raw query return * Updated deps * Corrected querier storage after funds transfer on execute * Removed prints * Fixed minor print error * Updated api in wasm-emulation querier * Fix clippy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some
multi-libentities are unit tested on their internal levels, instead of their actual exposed API, which could be improved to capture additional orchestration logic, and avoid depending on internals stability.It is follow up of CosmWasm/cw-plus#360
The text was updated successfully, but these errors were encountered: