[E2E] Allow testing with live-chain state#1949
Conversation
| tracing::error!("{}", err); | ||
| proc.kill().map_err(|e| { | ||
| format!("Error killing substrate process '{}': {}", proc.id(), e) | ||
| })?; |
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑These are the results when building the
Link to the run | Last update: Wed Nov 15 22:27:35 CET 2023 |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1949 +/- ##
==========================================
- Coverage 53.30% 53.24% -0.07%
==========================================
Files 219 219
Lines 6838 6844 +6
==========================================
- Hits 3645 3644 -1
- Misses 3193 3200 +7 ☔ View full report in Codecov by Sentry. |
CHANGELOG.md
Outdated
| - [E2E] Allow testing with live-chain state - [#1949](https://github.com/paritytech/ink/pull/1949) | ||
| - Stabilize `call_runtime` ‒ [#1749](https://github.com/paritytech/ink/pull/1749) | ||
| - Schema generation - [#1765](https://github.com/paritytech/ink/pull/1765) | ||
| - Add `set_block_number` to off-chain test api `Engine` - [#1806](https://github.com/paritytech/ink/pull/1806) |
There was a problem hiding this comment.
Was it intentional to add all those unrelated ones here?
There was a problem hiding this comment.
No, just a mistake during merge
|
On my branch I had added the feature to more |
Yes. I have run tests with |
Did you also run them with |
Yes, as you can see in git diff in this PR, |
ascjones
left a comment
There was a problem hiding this comment.
Can you give a brief explanation of the changes and the setup, and how it works to enable testing live-chain state?
Summary
Closes #1947
cargo-contractorpallet-contracts?Allows to run E2E tests against the live chain leveraging its live state
How to test
Due to the inability to run the test on GH workflow, here are instructions on how to run the test locally:
Copied from use-ink/ink-docs#283
dev.ymlconfig file in the repo or create one from scratch that you can reference later:Basically produce two empty blocks by submitting 2
system.remark(0)extrinsics on polkadot.jsintegration-tests/e2e-call-runtimeand modify the test attribute:cargo test -F e2e-testsChecklist before requesting a review
CHANGELOG.md