Add P<>K bridge manual zombienet test for asset transfer #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
serban300
force-pushed
the
bridge-zombienet-packaging
branch
2 times, most recently
from
81831b0
to
acf1797
Compare
acatangiu
approved these changes
Mar 6, 2024
|
/merge |
|
Enabled Available commands
For more information see the documentation |
auto-merge was automatically disabled
May 1, 2024 11:58
Head branch was pushed to by a user without write access
serban300
force-pushed
the
bridge-zombienet-packaging
branch
from
154e9d9
to
e840ed1
Compare
|
/merge |
fellowship-merge-bot
bot
merged commit 6d5a7a1
into
polkadot-fellows:main
36 checks passed
|
Enabled Available commands
For more information see the documentation |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a P<>K bridge zombienet test which checks the following:
The test is meant to be ran manually as per the instructions in the
README.mdand is based on the naive bridge testing "orchestrator" defined in thepolkadot-sdkrepo: https://github.com/paritytech/polkadot-sdk/tree/master/bridges/testing . The "orchestrator" is downloaded usinggit sparse checkoutdirectly from thepolkadot-sdkrepo (I couldn't find a better way to package thebashandjsfiles on which the test depends).Proposing to add the test in this repo as per the feedback from the bridges team and since this way it would be more convenient to run it before a release or when performing a change to the bridge hubs for example. If there are concerns about this, the second option would be to add it to the
parity-bridges-commonrepo.Closes: paritytech/polkadot-sdk#3400