Binary targets are automatically built if there is an integration test or
benchmark. This allows an integration test to execute the binary to exercise
-and test its behavior. The `CARGO_bin_EXE_<name>`
+and test its behavior. The `CARGO_BIN_EXE_<name>`
[environment variable](../reference/environment-variables.html#environment-variables-cargo-sets-for-crates)
is set when the integration test is built so that it can use the
[`env` macro](https://doc.rust-lang.org/std/macro.env.html) to locate the
Binary targets are automatically built if there is an integration test
or benchmark. This allows an integration test to execute the binary to
- exercise and test its behavior. The CARGO_bin_EXE_<name> environment
+ exercise and test its behavior. The CARGO_BIN_EXE_<name> environment
variable
<https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates>
is set when the integration test is built so that it can use the env
Binary targets are automatically built if there is an integration test or
benchmark. This allows an integration test to execute the binary to exercise
-and test its behavior. The `CARGO_bin_EXE_<name>`
+and test its behavior. The `CARGO_BIN_EXE_<name>`
[environment variable](../reference/environment-variables.html#environment-variables-cargo-sets-for-crates)
is set when the integration test is built so that it can use the
[`env` macro](https://doc.rust-lang.org/std/macro.env.html) to locate the
.sp
Binary targets are automatically built if there is an integration test or
benchmark. This allows an integration test to execute the binary to exercise
-and test its behavior. The \fBCARGO_bin_EXE_<name>\fR
+and test its behavior. The \fBCARGO_BIN_EXE_<name>\fR
\fIenvironment variable\fR <https://doc.rust\-lang.org/cargo/reference/environment\-variables.html#environment\-variables\-cargo\-sets\-for\-crates>
is set when the integration test is built so that it can use the
\fI\f(BIenv\fI macro\fR <https://doc.rust\-lang.org/std/macro.env.html> to locate the