-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
Migrate sui-move shell tests to sui crate #20995
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
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.
Changes look great to me. I'm super excited to see us finally start to have something where we can write tests more easily for the CLI.
#[tokio::main] | ||
async fn test_shell_snapshot(path: &Path) -> datatest_stable::Result<()> { | ||
// set up test cluster | ||
let cluster = if path.starts_with(TEST_NET_DIR) { |
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.
should this be contains
? Unsure of the structure of path
here though, so maybe starts_with
is right too here.
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.
# fixing issue https://github.com/MystenLabs/sui/issues/6546
this seemed to be relevant to one test but now I see it in move_build_bytecode_with_address_resolution.sh
Good catch! This was a copy-paste error |
Description
This PR migrates the shell-script-based tests from
sui-move
tosui
, and extends the test runner to create a TestCluster for tests in a certain subdirectory. Some of the existing tests have been migrated fromcli_tests.rs
to the new infrastructure as well.Test plan
There are some dummy tests to make sure the infrastructure is working properly. I will manually check that CI is running them!
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.