-
Notifications
You must be signed in to change notification settings - Fork 428
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
[ink_e2e]
auto detect contracts to be built
#1691
Conversation
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑These are the results when building the
Link to the run | Last update: Thu Mar 2 14:08:17 CET 2023 |
Codecov Report
@@ Coverage Diff @@
## master #1691 +/- ##
==========================================
- Coverage 70.82% 70.54% -0.28%
==========================================
Files 205 205
Lines 6409 6431 +22
==========================================
- Hits 4539 4537 -2
- Misses 1870 1894 +24
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
…tract dependencies
[ink_e2e]
detect and build all contracts in workspace[ink_e2e]
auto detect contracts to be built
@ascjones , how do I write e2e test where I have a dependency on a contract in its separate crate/github repository? Can I do it? |
Yes, it should work. As long as the code is available locally to build it should work. I assume when using a crate or github reference the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank youuuu.
Edit: Changelog plz :-)
Co-authored-by: Michael Müller <mich@elmueller.net>
0b9d16d
to
370120e
Compare
Currently the e2e test macro requires
additional_contracts
This PR:
additional_contracts
in the case where the contract manifests are already defined in the manifest.The way it determines whether a package is a contract is if the
ink-as-dependency
feature is defined. If a contract does not define this feature then it will not be recognised as being a contract. If this feature is defined for a package which is not a contract then the build will fail.If
additional_contracts
is specified it will behave as it currently does for backwards compatibility.