Skip to content
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

[transactional-test-runner] Document how run_test compares the output of a .move file against an expected output .exp #5125

Open
Tracked by #1979
miker83z opened this issue Jan 31, 2025 · 0 comments · May be fixed by #5171
Assignees
Labels
vm-language Issues related to the VM & Language Team
Milestone

Comments

@miker83z
Copy link
Contributor

miker83z commented Jan 31, 2025

Stems from #1979 (comment)

Document that the output produced by each .move file will get matched against the expected output defined in the respective .exp file:

pub async fn run_test_impl<'a, Adapter>(
    path: &Path,
    fully_compiled_program_opt: Option<Arc<FullyCompiledProgram>>,
) -> Result<(), Box<dyn std::error::Error>>
where
    Adapter: MoveTestAdapter<'a>,
    Adapter::ExtraInitArgs: Debug,
    Adapter::ExtraPublishArgs: Debug,
    Adapter::ExtraValueArgs: Debug,
    Adapter::ExtraRunArgs: Debug,
    Adapter::Subcommand: Debug,
{
    let output = handle_actual_output::<Adapter>(path, fully_compiled_program_opt).await?;
    handle_expected_output(path, output.0)?;
    Ok(())
}
  • This is independent of subcommands and can fit into the general section
  • Describe the whole process
  • Describe the structure of the .move file
  • Describe the structure of the .exp file
@miker83z miker83z added the vm-language Issues related to the VM & Language Team label Jan 31, 2025
@miker83z miker83z added this to the Mainnet milestone Jan 31, 2025
@Dkwcs Dkwcs linked a pull request Feb 3, 2025 that will close this issue
@Dkwcs Dkwcs linked a pull request Feb 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vm-language Issues related to the VM & Language Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants