-
Notifications
You must be signed in to change notification settings - Fork 430
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
Advanced test environment #1589
base: master
Are you sure you want to change the base?
Advanced test environment #1589
Conversation
…t' into feature/advanced-test-environment # Conflicts: # crates/env/src/api.rs # crates/env/src/backend.rs # crates/ink/codegen/src/generator/dispatch.rs
Codecov Report
@@ Coverage Diff @@
## master #1589 +/- ##
==========================================
- Coverage 70.44% 69.56% -0.89%
==========================================
Files 207 207
Lines 6398 6548 +150
==========================================
+ Hits 4507 4555 +48
- Misses 1891 1993 +102
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@Artemka374 thanks for the PR, sorry for leaving it sitting around so long. Tbh not sure when we'll have time to review this since it's a non-trivial addition |
Hi @HCastano thanks for the reply. We understand that there is so much going on in ink! right now, I will just point out that this is a demanded feature and would make development (and testing especially) much easier for devs. We will keep maintaining this PR and are happy to hear some feedback when you will have time to get to this 😄 |
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑
These are the results when building the
Link to the run | Last update: Wed Mar 1 13:40:10 CET 2023 |
@Artemka374 Could you clarify the following:
Is this the main intention for the PR? Because we have released ink! 4.0 in the meantime and E2E testing supports this by default. The reason I'm asking is because the PR has 1k lines of code and there is some maintenance costs associated with it. We're thinking about what functionality to support in the off-chain testing engine and for which to require usage of the E2E testing. |
@cmichi Actually, it is more like full implementation of off-chain functionality, that wasn't accessible before, but I think off-chain cross-contract calls testing is the most important part of it. |
I think this is superseeded by what's being enabled with #1864 . |
Using off-chain environment though, right? Not the actual one on which the contract will be ran after deployment. |
Exactly |
This is PR for this issue: Supercolony-net/openbrush-contracts#136 (comment)
that was started in Supercolony-net#4
It allows testing cross-contract calls in off-chain environment