How to find binary from integration test?

Is there a cleaner way to find a binary executable from an integration test other than looking at `current_exe()` and finding it from there?  Cargo itself uses this logic:

https://github.com/rust-lang/cargo/blob/848250597527659dd54b533c3d35d6505dd60a20/tests/testsuite/cargotest/support/mod.rs#L392-L409

I've seen others use `Command::new("./target/debug/NAME")` which can fail in some cases.

It seems like this should be easier.  Am I missing a better way?  If not, would it make sense to provide some method to more easily find binaries?

	pub fn cargo_dir() -> PathBuf {
	env::var_os("CARGO_BIN_PATH")
	.map(PathBuf::from)
	.or_else(\|\| {
	env::current_exe().ok().map(\|mut path\| {
	path.pop();
	if path.ends_with("deps") {
	path.pop();
	}
	path
	})
	})
	.unwrap_or_else(\|\| panic!("CARGO_BIN_PATH wasn't set. Cannot continue running test"))
	}

	pub fn cargo_exe() -> PathBuf {
	cargo_dir().join(format!("cargo{}", env::consts::EXE_SUFFIX))
	}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

How to find binary from integration test? #5758

ehuss
openedon Jul 21, 2018

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

How to find binary from integration test? #5758

Description

ehussopenedon Jul 21, 2018

Metadata