-
Notifications
You must be signed in to change notification settings - Fork 105
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
Improve runtime tests #1001
Improve runtime tests #1001
Conversation
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.
Nice! 🚀
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1001 +/- ##
==========================================
+ Coverage 81.14% 81.23% +0.09%
==========================================
Files 53 53
Lines 2132 2132
Branches 72 72
==========================================
+ Hits 1730 1732 +2
+ Misses 387 385 -2
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Excellent!
@claravanstaden I've moved the tests in Snowfork/polkadot-sdk#17 to our own repo and made some fix. To seperate from cumulus it's more convenient to maintain/extend tests as required IMO. |
c0b8ba5
to
4e1d39a
Compare
parachain/runtime-tests/Cargo.toml
Outdated
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.
Can we make this small change. Move this crate to directory parachain/runtime/tests/Cargo.toml
.
Since @alistair-singh is also introducing a runtime-common
crate, we should put all the runtime specific crates under parachain/runtime
.
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.
--manifest-path polkadot-sdk/Cargo.toml | ||
-p bridge-hub-rococo-integration-tests | ||
-p bridge-hub-rococo-integration-tests snowbridge |
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.
What package is named snowbridge
? I don't recall any package like that?
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.
Actually it's not a package name, the mod name to filter snowbrige tests only.
@@ -12,6 +12,6 @@ members = [ | |||
"pallets/ethereum-beacon-client", | |||
"pallets/control", | |||
"pallets/control/runtime-api", | |||
"runtime/tests", |
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.
The tests crate is only used by the runtimes in polkadot-sdk/
, so I don't think we should add it to the cargo workspace. We're effectively creating some kind of cyclical dependency loop here :)
Also because its going to bloat our local compile times.
When I run cargo test
, I just want to run tests for our pallets and primitives crates. Not runtime-specific stuff.
So its fine for the crate to have its own Cargo.lock
.
No description provided.