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

Migrate CLI tests to use the testbed pre-configured organizations #9144

Open
vxgmichel opened this issue Dec 9, 2024 · 0 comments
Open

Migrate CLI tests to use the testbed pre-configured organizations #9144

vxgmichel opened this issue Dec 9, 2024 · 0 comments
Labels
A-Client Area: Parsec desktop application I-CLI Impact: Command-line interface I-Rust Impact: Rust-related stuff

Comments

@vxgmichel
Copy link
Contributor

The CLI tests use testenv_utils::initialize_test_organization instead of relying on the templated testbed organizations (minimalorg, coolorg and shamirorg):

async fn run_local_organization(
tmp_dir: &Path,
source_file: Option<PathBuf>,
config: TestenvConfig,
) -> anyhow::Result<(ParsecAddr, TestOrganization, OrganizationID)> {
let url = new_environment(tmp_dir, source_file, config, false)
.await?
.unwrap();
println!("Initializing test organization to {url}");
let org_id = unique_org_id();
initialize_test_organization(ClientConfig::default(), url.clone(), org_id.clone())
.await
.map(|v| (url, v, org_id))
}

Let's consider migrating the CLI tests to those pre-configured testbed organizations.

@FirelightFlagboy FirelightFlagboy added I-Rust Impact: Rust-related stuff A-Client Area: Parsec desktop application I-CLI Impact: Command-line interface labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client Area: Parsec desktop application I-CLI Impact: Command-line interface I-Rust Impact: Rust-related stuff
Projects
None yet
Development

No branches or pull requests

2 participants