I have an integ test which relies on spawning child processes of other crates in my workspace, but cargo doesn't automatically build those for integ tests - it only builds the crate the integ is for.
How can I get cargo to build these automatically / rebuild them when their contents change?
This sounds like a use-case for Cargo's unstable artifact dependencies.
Yeah, that would be ideal, but I don't expect that to be stabilized anytime soon looking at the GitHub issue.
If the binaries are inside the same package as the integration test, you can use the env!("CARGO_BIN_EXE_some_bin_name") to get the path of these binaries when building the integration test.
Binary targets are automatically built if there is an integration test. This allows an integration test to execute the binary to exercise and test its behavior. The
CARGO_BIN_EXE_<name>environment variable is set when the integration test is built so that it can use theenvmacro to locate the executable.
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.