Skip to content

Commit 553a883

Browse files
committed
[site] fix up help text in a couple more spots
1 parent fb52010 commit 553a883

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

site/src/book/env-vars.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,9 @@ cargo-nextest exposes these environment variables to your tests *at runtime only
2929

3030
* `NEXTEST` — always set to `"1"`.
3131
* `NEXTEST_EXECUTION_MODE` — currently, always set to `process-per-test`. More options may be added in the future if nextest gains the ability to run all tests within the same process ([#27]).
32-
* `NEXTEST_BIN_EXE_<name>`: The absolute path to a binary target's executable. This is only set when running an [integration test] or benchmark. The `<name>` is the name of the binary target, exactly as-is. For example, `NEXTEST_BIN_EXE_my-program` for a binary named `my-program`. Binaries are automatically built when the test is built, unless the binary has required features that are not enabled.
32+
* `NEXTEST_BIN_EXE_<name>`: The absolute path to a binary target's executable. This is only set when running an [integration test] or benchmark. The `<name>` is the name of the binary target, exactly as-is. For example, `NEXTEST_BIN_EXE_my-program` for a binary named `my-program`.
33+
* Binaries are automatically built when the test is built, unless the binary has required features that are not enabled.
34+
* When [reusing builds](reusing-builds.md) from an archive, this is set to the remapped path within the target directory.
3335

3436
[#27]: https://github.com/nextest-rs/nextest/issues/27
3537
[integration test]: https://doc.rust-lang.org/cargo/reference/cargo-targets.html#integration-tests
@@ -41,7 +43,7 @@ cargo-nextest delegates to Cargo for the build, which controls the environment v
4143
cargo-nextest also sets these environment variables at runtime, matching the behavior of cargo test:
4244

4345
* `CARGO` — Path to the `cargo` binary performing the build.
44-
* `CARGO_MANIFEST_DIR` — The directory containing the manifest of your package. If [`--workspace-remap`](reusing-builds.md#new-options) is passed in, this is set to the remapped manifest directory. You can obtain the non-remapped directory using the value of this variable at compile-time, e.g. `env!("CARGO_MANIFEST_DIR")`.
46+
* `CARGO_MANIFEST_DIR` — The directory containing the manifest of your package. If [`--workspace-remap`](reusing-builds.md#specifying-a-new-location-for-the-workspace) is passed in, this is set to the remapped manifest directory. You can obtain the non-remapped directory using the value of this variable at compile-time, e.g. `env!("CARGO_MANIFEST_DIR")`.
4547
* `CARGO_PKG_VERSION` — The full version of your package.
4648
* `CARGO_PKG_VERSION_MAJOR` — The major version of your package.
4749
* `CARGO_PKG_VERSION_MINOR` — The minor version of your package.

0 commit comments

Comments
 (0)