-
Notifications
You must be signed in to change notification settings - Fork 443
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
Implemented contract instantiation and invocation for integration tests #1988
Implemented contract instantiation and invocation for integration tests #1988
Conversation
# Conflicts: # crates/env/src/lib.rs # crates/env/src/reflect/event.rs # crates/ink/codegen/Cargo.toml
Moved reflection, contract, arithmetic, and miscellaneous types from ink_env to ink_primitives.
This reverts commit 2d1950a.
…tation # Conflicts: # crates/engine/src/database.rs
@Helios-vmg Could you merge |
…ation # Conflicts: # CHANGELOG.md # crates/engine/src/database.rs # crates/env/Cargo.toml # crates/env/src/call/call_builder.rs # crates/env/src/call/create_builder.rs # crates/env/src/engine/off_chain/impls.rs # crates/env/src/engine/off_chain/mod.rs # crates/env/src/engine/on_chain/impls/pallet_contracts.rs # crates/env/src/lib.rs # crates/ink/codegen/Cargo.toml # crates/ink/macro/Cargo.toml # crates/primitives/Cargo.toml
@cmichi Done. Some notes:
Likewise, running |
@Helios-vmg Thanks a lot for the PR and the merge of |
Summary
cargo-contract
orpallet-contracts
?This PR implements instantiate_contract(), invoke_contract(), invoke_contract_delegate() and a few other functions for the integration testing environment. More specifically, it permits calling these functions from inside contracts transparently, as if the contract was running on the blockchain.
Description
()
, instead of!
. A further modification was needed on execute_dispatchable() to avoid a compiler error when return_value() doesn't return!
. When test_instantiate is enabled, AnOk(())
is added at the end of the functions (for constructor as well as for message dispatch), thus allowing the test-case to proceed.CHANGELOG.md
Other notes
To test a contract that uses instantiate_contract() in the off-chain environment, use
cargo test --features test_instantiate
.Regarding the build errors in the doc tests, I've been trying to resolve them, but it's difficult without any way to see the macro expansion. When I move the code inside the comments to an actual contract it compiles correctly. Is there any way to move forward with this? Can I mark the comments as no_compile and add equivalent integration tests to catch breaking changes?