Skip to content

Running benchmarks

0.9.117

Experimental: This feature is not yet stable

  • Enable with: Add experimental = ["benchmarks"] to .config/nextest.toml, or set NEXTEST_EXPERIMENTAL_BENCHMARKS=1 in the environment
  • Tracking issue: #2874

Nextest supports running benchmarks with the cargo nextest bench command. Using cargo nextest bench can be helpful in case your benchmarks require setup or wrapper scripts.

Supported benchmark harnesses include:

Note

This page is about running benchmarks to measure performance. Benchmarks can also be run in test mode as regular tests via cargo nextest run, without requiring an experimental feature flag. For more, see Criterion benchmarks.

Benchmark-specific settings

Since benchmarks typically take longer than tests to run, nextest applies a different set of slow and global timeouts for them. Access these via the bench.slow-timeout and bench.global-timeout settings, respectively.

Setting timeouts for benchmarks
[profile.default]
# Set a global timeout of 2 hours for benchmarks.
bench.global-timeout = "2h"

[profile.default.overrides]
# Terminate this benchmark after 10 minutes.
filter = "test(bench_commands)"
bench.slow-timeout = { period = "60s", terminate-after = 10 }

The regular slow-timeout and global-timeout settings are ignored for benchmarks.

Options and arguments

The output of cargo nextest bench -h:

Build and run benchmarks (experimental)

Usage: cargo nextest bench [OPTIONS] [FILTERS]... [-- <FILTERS_AND_ARGS>...]

Arguments:
  [FILTERS]...           Test name filters
  [FILTERS_AND_ARGS]...  Test name filters and emulated test binary arguments

Options:
      --color <WHEN>  Produce color output: auto, always, never [env: CARGO_TERM_COLOR=always]
                      [default: auto]
      --no-pager      Do not pipe output through a pager
  -v, --verbose       Verbose output [env: NEXTEST_VERBOSE=]
  -h, --help          Print help (see more with '--help')

Package selection:
  -p, --package <PACKAGES>  Package to test
      --workspace           Test all packages in the workspace
      --exclude <EXCLUDE>   Exclude packages from the test
      --all                 Alias for --workspace (deprecated)

Target selection:
      --lib                Test only this package's library unit tests
      --bin <BIN>          Test only the specified binary
      --bins               Test all binaries
      --example <EXAMPLE>  Test only the specified example
      --examples           Test all examples
      --test <TEST>        Test only the specified test target
      --tests              Test all targets
      --bench <BENCH>      Test only the specified bench target
      --benches            Test all benches
      --all-targets        Test all targets

Feature selection:
  -F, --features <FEATURES>  Space or comma separated list of features to activate
      --all-features         Activate all available features
      --no-default-features  Do not activate the default feature

Compilation options:
      --build-jobs <N>        Number of build jobs to run
  -r, --release               Build artifacts in release mode, with optimizations
      --cargo-profile <NAME>  Build artifacts with the specified Cargo profile
      --target <TRIPLE>       Build for the target triple
      --target-dir <DIR>      Directory for all generated artifacts
      --unit-graph            Output build graph in JSON (unstable)
      --timings[=<FMTS>]      Timing output formats (unstable) (comma separated): html, json

Manifest options:
      --manifest-path <PATH>  Path to Cargo.toml
      --frozen                Require Cargo.lock and cache are up to date
      --locked                Require Cargo.lock is up to date
      --offline               Run without accessing the network

Other Cargo options:
      --cargo-quiet...          Do not print cargo log messages (specify twice for no Cargo output
                                at all)
      --cargo-verbose...        Use cargo verbose output (specify twice for very verbose/build.rs
                                output)
      --ignore-rust-version     Ignore rust-version specification in packages
      --future-incompat-report  Outputs a future incompatibility report at the end of the build
      --config <KEY=VALUE>      Override a Cargo configuration value
  -Z <FLAG>                     Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for
                                details

Filter options:
      --run-ignored <WHICH>    Run ignored tests [possible values: default, only, all]
      --partition <PARTITION>  Test partition, e.g. hash:1/2 or count:2/3
  -E, --filterset <EXPR>       Test filterset (see 
                               https://nexte.st/docs/filtersets)
      --ignore-default-filter  Ignore the default filter configured in the profile

Runner options:
      --no-run             Compile, but don't run benchmarks
      --fail-fast          Cancel benchmark run on the first failure [aliases: --ff]
      --no-fail-fast       Run all benchmarks regardless of failure [aliases: --nff]
      --max-fail <N>       Number of benchmarks that can fail before exiting run [possible values:
                           integer or "all"]
      --no-tests <ACTION>  Behavior if there are no benchmarks to run [default: fail] [env:
                           NEXTEST_NO_TESTS=] [possible values: pass, warn, fail]
      --no-capture         Run benchmarks serially and do not capture output (always enabled)

Stress testing options:
      --stress-count <COUNT>        The number of times to run each test, or infinite to run
                                    indefinitely
      --stress-duration <DURATION>  How long to run stress tests until (e.g. 24h)
      --debugger <DEBUGGER>         Debug a single test using a text-based or graphical debugger
      --tracer <TRACER>             Trace a single test using a syscall tracer like strace or truss

Reporter options:
      --show-progress <SHOW_PROGRESS>  Show nextest progress in the specified manner [env:
                                       NEXTEST_SHOW_PROGRESS=] [possible values: auto, none, bar,
                                       counter, only]
      --no-input-handler               Disable handling of input keys from the terminal [env:
                                       NEXTEST_NO_INPUT_HANDLER=]

Config options:
      --config-file <PATH>
          Config file [default: workspace-root/.config/nextest.toml]
      --tool-config-file <TOOL:ABS_PATH>
          Tool-specific config files
      --override-version-check
          Override checks for the minimum version defined in nextest's config
  -P, --profile <PROFILE>
          The nextest profile to use [env: NEXTEST_PROFILE=]
Build and run benchmarks (experimental)

Usage: cargo nextest bench [OPTIONS] [FILTERS]... [-- <FILTERS_AND_ARGS>...]

Arguments:
  [FILTERS]...           Test name filters
  [FILTERS_AND_ARGS]...  Test name filters and emulated test binary arguments

Options:
      --color <WHEN>  Produce color output: auto, always, never [env: CARGO_TERM_COLOR=always]
                      [default: auto]
      --no-pager      Do not pipe output through a pager
  -v, --verbose       Verbose output [env: NEXTEST_VERBOSE=]
  -h, --help          Print help (see more with '--help')

Package selection:
  -p, --package <PACKAGES>  Package to test
      --workspace           Test all packages in the workspace
      --exclude <EXCLUDE>   Exclude packages from the test
      --all                 Alias for --workspace (deprecated)

Target selection:
      --lib                Test only this package's library unit tests
      --bin <BIN>          Test only the specified binary
      --bins               Test all binaries
      --example <EXAMPLE>  Test only the specified example
      --examples           Test all examples
      --test <TEST>        Test only the specified test target
      --tests              Test all targets
      --bench <BENCH>      Test only the specified bench target
      --benches            Test all benches
      --all-targets        Test all targets

Feature selection:
  -F, --features <FEATURES>  Space or comma separated list of features to activate
      --all-features         Activate all available features
      --no-default-features  Do not activate the default feature

Compilation options:
      --build-jobs <N>        Number of build jobs to run
  -r, --release               Build artifacts in release mode, with optimizations
      --cargo-profile <NAME>  Build artifacts with the specified Cargo profile
      --target <TRIPLE>       Build for the target triple
      --target-dir <DIR>      Directory for all generated artifacts
      --unit-graph            Output build graph in JSON (unstable)
      --timings[=<FMTS>]      Timing output formats (unstable) (comma separated): html, json

Manifest options:
      --manifest-path <PATH>  Path to Cargo.toml
      --frozen                Require Cargo.lock and cache are up to date
      --locked                Require Cargo.lock is up to date
      --offline               Run without accessing the network

Other Cargo options:
      --cargo-quiet...          Do not print cargo log messages (specify twice for no Cargo output
                                at all)
      --cargo-verbose...        Use cargo verbose output (specify twice for very verbose/build.rs
                                output)
      --ignore-rust-version     Ignore rust-version specification in packages
      --future-incompat-report  Outputs a future incompatibility report at the end of the build
      --config <KEY=VALUE>      Override a Cargo configuration value
  -Z <FLAG>                     Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for
                                details

Filter options:
      --run-ignored <WHICH>    Run ignored tests [possible values: default, only, all]
      --partition <PARTITION>  Test partition, e.g. hash:1/2 or count:2/3
  -E, --filterset <EXPR>       Test filterset (see 
                               https://nexte.st/docs/filtersets)
      --ignore-default-filter  Ignore the default filter configured in the profile

Runner options:
      --no-run             Compile, but don't run benchmarks
      --fail-fast          Cancel benchmark run on the first failure [aliases: --ff]
      --no-fail-fast       Run all benchmarks regardless of failure [aliases: --nff]
      --max-fail <N>       Number of benchmarks that can fail before exiting run [possible values:
                           integer or "all"]
      --no-tests <ACTION>  Behavior if there are no benchmarks to run [default: fail] [env:
                           NEXTEST_NO_TESTS=] [possible values: pass, warn, fail]
      --no-capture         Run benchmarks serially and do not capture output (always enabled)

Stress testing options:
      --stress-count <COUNT>        The number of times to run each test, or infinite to run
                                    indefinitely
      --stress-duration <DURATION>  How long to run stress tests until (e.g. 24h)
      --debugger <DEBUGGER>         Debug a single test using a text-based or graphical debugger
      --tracer <TRACER>             Trace a single test using a syscall tracer like strace or truss

Reporter options:
      --show-progress <SHOW_PROGRESS>  Show nextest progress in the specified manner [env:
                                       NEXTEST_SHOW_PROGRESS=] [possible values: auto, none, bar,
                                       counter, only]
      --no-input-handler               Disable handling of input keys from the terminal [env:
                                       NEXTEST_NO_INPUT_HANDLER=]

Config options:
      --config-file <PATH>
          Config file [default: workspace-root/.config/nextest.toml]
      --tool-config-file <TOOL:ABS_PATH>
          Tool-specific config files
      --override-version-check
          Override checks for the minimum version defined in nextest's config
  -P, --profile <PROFILE>
          The nextest profile to use [env: NEXTEST_PROFILE=]

The output of cargo nextest bench --help:

Build and run benchmarks (experimental).

This command builds benchmark binaries and queries them for the benchmarks they contain, then runs
each benchmark serially.

This is an experimental feature. To enable it, set the environment variable 
NEXTEST_EXPERIMENTAL_BENCHMARKS=1.

Usage: cargo nextest bench [OPTIONS] [FILTERS]... [-- <FILTERS_AND_ARGS>...]

Arguments:
  [FILTERS]...
          Test name filters

  [FILTERS_AND_ARGS]...
          Test name filters and emulated test binary arguments.
          
          Supported arguments:
          
          - --ignored:         Only run ignored tests
          - --include-ignored: Run both ignored and non-ignored tests
          - --skip PATTERN:    Skip tests that match the pattern
          - --exact:           Run tests that exactly match patterns after --

Options:
      --color <WHEN>
          Produce color output: auto, always, never

          [env: CARGO_TERM_COLOR=always]
          [default: auto]

      --no-pager
          Do not pipe output through a pager

  -v, --verbose
          Verbose output

          [env: NEXTEST_VERBOSE=]

  -h, --help
          Print help (see a summary with '-h')

Package selection:
  -p, --package <PACKAGES>
          Package to test

      --workspace
          Test all packages in the workspace

      --exclude <EXCLUDE>
          Exclude packages from the test

      --all
          Alias for --workspace (deprecated)

Target selection:
      --lib
          Test only this package's library unit tests

      --bin <BIN>
          Test only the specified binary

      --bins
          Test all binaries

      --example <EXAMPLE>
          Test only the specified example

      --examples
          Test all examples

      --test <TEST>
          Test only the specified test target

      --tests
          Test all targets

      --bench <BENCH>
          Test only the specified bench target

      --benches
          Test all benches

      --all-targets
          Test all targets

Feature selection:
  -F, --features <FEATURES>
          Space or comma separated list of features to activate

      --all-features
          Activate all available features

      --no-default-features
          Do not activate the default feature

Compilation options:
      --build-jobs <N>
          Number of build jobs to run

  -r, --release
          Build artifacts in release mode, with optimizations

      --cargo-profile <NAME>
          Build artifacts with the specified Cargo profile

      --target <TRIPLE>
          Build for the target triple

      --target-dir <DIR>
          Directory for all generated artifacts

      --unit-graph
          Output build graph in JSON (unstable)

      --timings[=<FMTS>]
          Timing output formats (unstable) (comma separated): html, json

Manifest options:
      --manifest-path <PATH>
          Path to Cargo.toml

      --frozen
          Require Cargo.lock and cache are up to date

      --locked
          Require Cargo.lock is up to date

      --offline
          Run without accessing the network

Other Cargo options:
      --cargo-quiet...
          Do not print cargo log messages (specify twice for no Cargo output at all)

      --cargo-verbose...
          Use cargo verbose output (specify twice for very verbose/build.rs output)

      --ignore-rust-version
          Ignore rust-version specification in packages

      --future-incompat-report
          Outputs a future incompatibility report at the end of the build

      --config <KEY=VALUE>
          Override a Cargo configuration value

  -Z <FLAG>
          Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details

Filter options:
      --run-ignored <WHICH>
          Run ignored tests

          Possible values:
          - default: Run non-ignored tests
          - only:    Run ignored tests
          - all:     Run both ignored and non-ignored tests

      --partition <PARTITION>
          Test partition, e.g. hash:1/2 or count:2/3

      --platform-filter <PLATFORM>
          Filter test binaries by build platform (DEPRECATED).
          
          Instead, use -E with 'platform(host)' or 'platform(target)'.

          [default: any]
          [possible values: target, host, any]

  -E, --filterset <EXPR>
          Test filterset (see 
          https://nexte.st/docs/filtersets)

      --ignore-default-filter
          Ignore the default filter configured in the profile.
          
          By default, all filtersets are intersected with the default filter configured in the
          profile. This flag disables that behavior.
          
          This flag doesn't change the definition of the default() filterset.

Runner options:
      --no-run
          Compile, but don't run benchmarks

      --fail-fast
          Cancel benchmark run on the first failure

          [aliases: --ff]

      --no-fail-fast
          Run all benchmarks regardless of failure

          [aliases: --nff]

      --max-fail <N>
          Number of benchmarks that can fail before exiting run [possible values: integer or "all"]

      --no-tests <ACTION>
          Behavior if there are no benchmarks to run [default: fail]

          Possible values:
          - pass: Silently exit with code 0
          - warn: Produce a warning and exit with code 0
          - fail: Produce an error message and exit with code 4

          [env: NEXTEST_NO_TESTS=]

      --no-capture
          Run benchmarks serially and do not capture output (always enabled).
          
          Benchmarks in nextest always run serially, so this flag is kept only for compatibility and
          has no effect.

Stress testing options:
      --stress-count <COUNT>
          The number of times to run each test, or infinite to run indefinitely

      --stress-duration <DURATION>
          How long to run stress tests until (e.g. 24h)

      --debugger <DEBUGGER>
          Debug a single test using a text-based or graphical debugger.
          
          Debugger mode automatically:
          
          - disables timeouts
          - disables output capture
          - passes standard input through to the debugger
          
          Example: --debugger "rust-gdb --args"

      --tracer <TRACER>
          Trace a single test using a syscall tracer like strace or truss.
          
          Tracer mode automatically:
          
          - disables timeouts
          - disables output capture
          
          Unlike --debugger, tracers do not need stdin passthrough or special signal handling.
          
          Example: --tracer "strace -tt"

Reporter options:
      --show-progress <SHOW_PROGRESS>
          Show nextest progress in the specified manner.
          
          For benchmarks, the default is "counter" which shows the benchmark index (e.g., "(1/10)")
          but no progress bar.
          
          This can also be set via user config at ~/.config/nextest/config.toml. See 
          https://nexte.st/docs/user-config.

          Possible values:
          - auto:    Automatically choose the best progress display based on whether nextest is
            running in an interactive terminal
          - none:    Do not display a progress bar or counter
          - bar:     Display a progress bar with running tests: default for interactive terminals
          - counter: Display a counter next to each completed test
          - only:    Display a progress bar with running tests, and hide successful test output;
            equivalent to --show-progress=running --status-level=slow --final-status-level=none

          [env: NEXTEST_SHOW_PROGRESS=]

      --no-input-handler
          Disable handling of input keys from the terminal.
          
          By default, when running a terminal, nextest accepts the t key to dump test information.
          This flag disables that behavior.

          [env: NEXTEST_NO_INPUT_HANDLER=]

Config options:
      --config-file <PATH>
          Config file [default: workspace-root/.config/nextest.toml]

      --tool-config-file <TOOL:ABS_PATH>
          Tool-specific config files.
          
          Some tools on top of nextest may want to set up their own default configuration but
          prioritize user configuration on top. Use this argument to insert configuration that's
          lower than --config-file in priority but above the default config shipped with nextest.
          
          Arguments are specified in the format "tool:abs_path", for example
          "my-tool:/path/to/nextest.toml" (or "my-tool:C:\path\to\nextest.toml" on Windows). Paths
          must be absolute.
          
          This argument may be specified multiple times. Files that come later are lower priority
          than those that come earlier.

      --override-version-check
          Override checks for the minimum version defined in nextest's config.
          
          Repository and tool-specific configuration files can specify minimum required and
          recommended versions of nextest. This option overrides those checks.

  -P, --profile <PROFILE>
          The nextest profile to use.
          
          Nextest's configuration supports multiple profiles, which can be used to set up different
          configurations for different purposes. (For example, a configuration for local runs and
          one for CI.) This option selects the profile to use.

          [env: NEXTEST_PROFILE=]
Build and run benchmarks (experimental).

This command builds benchmark binaries and queries them for the benchmarks they contain, then runs
each benchmark serially.

This is an experimental feature. To enable it, set the environment variable 
NEXTEST_EXPERIMENTAL_BENCHMARKS=1.

Usage: cargo nextest bench [OPTIONS] [FILTERS]... [-- <FILTERS_AND_ARGS>...]

Arguments:
  [FILTERS]...
          Test name filters

  [FILTERS_AND_ARGS]...
          Test name filters and emulated test binary arguments.
          
          Supported arguments:
          
          - --ignored:         Only run ignored tests
          - --include-ignored: Run both ignored and non-ignored tests
          - --skip PATTERN:    Skip tests that match the pattern
          - --exact:           Run tests that exactly match patterns after --

Options:
      --color <WHEN>
          Produce color output: auto, always, never

          [env: CARGO_TERM_COLOR=always]
          [default: auto]

      --no-pager
          Do not pipe output through a pager

  -v, --verbose
          Verbose output

          [env: NEXTEST_VERBOSE=]

  -h, --help
          Print help (see a summary with '-h')

Package selection:
  -p, --package <PACKAGES>
          Package to test

      --workspace
          Test all packages in the workspace

      --exclude <EXCLUDE>
          Exclude packages from the test

      --all
          Alias for --workspace (deprecated)

Target selection:
      --lib
          Test only this package's library unit tests

      --bin <BIN>
          Test only the specified binary

      --bins
          Test all binaries

      --example <EXAMPLE>
          Test only the specified example

      --examples
          Test all examples

      --test <TEST>
          Test only the specified test target

      --tests
          Test all targets

      --bench <BENCH>
          Test only the specified bench target

      --benches
          Test all benches

      --all-targets
          Test all targets

Feature selection:
  -F, --features <FEATURES>
          Space or comma separated list of features to activate

      --all-features
          Activate all available features

      --no-default-features
          Do not activate the default feature

Compilation options:
      --build-jobs <N>
          Number of build jobs to run

  -r, --release
          Build artifacts in release mode, with optimizations

      --cargo-profile <NAME>
          Build artifacts with the specified Cargo profile

      --target <TRIPLE>
          Build for the target triple

      --target-dir <DIR>
          Directory for all generated artifacts

      --unit-graph
          Output build graph in JSON (unstable)

      --timings[=<FMTS>]
          Timing output formats (unstable) (comma separated): html, json

Manifest options:
      --manifest-path <PATH>
          Path to Cargo.toml

      --frozen
          Require Cargo.lock and cache are up to date

      --locked
          Require Cargo.lock is up to date

      --offline
          Run without accessing the network

Other Cargo options:
      --cargo-quiet...
          Do not print cargo log messages (specify twice for no Cargo output at all)

      --cargo-verbose...
          Use cargo verbose output (specify twice for very verbose/build.rs output)

      --ignore-rust-version
          Ignore rust-version specification in packages

      --future-incompat-report
          Outputs a future incompatibility report at the end of the build

      --config <KEY=VALUE>
          Override a Cargo configuration value

  -Z <FLAG>
          Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details

Filter options:
      --run-ignored <WHICH>
          Run ignored tests

          Possible values:
          - default: Run non-ignored tests
          - only:    Run ignored tests
          - all:     Run both ignored and non-ignored tests

      --partition <PARTITION>
          Test partition, e.g. hash:1/2 or count:2/3

      --platform-filter <PLATFORM>
          Filter test binaries by build platform (DEPRECATED).
          
          Instead, use -E with 'platform(host)' or 'platform(target)'.

          [default: any]
          [possible values: target, host, any]

  -E, --filterset <EXPR>
          Test filterset (see 
          https://nexte.st/docs/filtersets)

      --ignore-default-filter
          Ignore the default filter configured in the profile.
          
          By default, all filtersets are intersected with the default filter configured in the
          profile. This flag disables that behavior.
          
          This flag doesn't change the definition of the default() filterset.

Runner options:
      --no-run
          Compile, but don't run benchmarks

      --fail-fast
          Cancel benchmark run on the first failure

          [aliases: --ff]

      --no-fail-fast
          Run all benchmarks regardless of failure

          [aliases: --nff]

      --max-fail <N>
          Number of benchmarks that can fail before exiting run [possible values: integer or "all"]

      --no-tests <ACTION>
          Behavior if there are no benchmarks to run [default: fail]

          Possible values:
          - pass: Silently exit with code 0
          - warn: Produce a warning and exit with code 0
          - fail: Produce an error message and exit with code 4

          [env: NEXTEST_NO_TESTS=]

      --no-capture
          Run benchmarks serially and do not capture output (always enabled).
          
          Benchmarks in nextest always run serially, so this flag is kept only for compatibility and
          has no effect.

Stress testing options:
      --stress-count <COUNT>
          The number of times to run each test, or infinite to run indefinitely

      --stress-duration <DURATION>
          How long to run stress tests until (e.g. 24h)

      --debugger <DEBUGGER>
          Debug a single test using a text-based or graphical debugger.
          
          Debugger mode automatically:
          
          - disables timeouts
          - disables output capture
          - passes standard input through to the debugger
          
          Example: --debugger "rust-gdb --args"

      --tracer <TRACER>
          Trace a single test using a syscall tracer like strace or truss.
          
          Tracer mode automatically:
          
          - disables timeouts
          - disables output capture
          
          Unlike --debugger, tracers do not need stdin passthrough or special signal handling.
          
          Example: --tracer "strace -tt"

Reporter options:
      --show-progress <SHOW_PROGRESS>
          Show nextest progress in the specified manner.
          
          For benchmarks, the default is "counter" which shows the benchmark index (e.g., "(1/10)")
          but no progress bar.
          
          This can also be set via user config at ~/.config/nextest/config.toml. See 
          https://nexte.st/docs/user-config.

          Possible values:
          - auto:    Automatically choose the best progress display based on whether nextest is
            running in an interactive terminal
          - none:    Do not display a progress bar or counter
          - bar:     Display a progress bar with running tests: default for interactive terminals
          - counter: Display a counter next to each completed test
          - only:    Display a progress bar with running tests, and hide successful test output;
            equivalent to --show-progress=running --status-level=slow --final-status-level=none

          [env: NEXTEST_SHOW_PROGRESS=]

      --no-input-handler
          Disable handling of input keys from the terminal.
          
          By default, when running a terminal, nextest accepts the t key to dump test information.
          This flag disables that behavior.

          [env: NEXTEST_NO_INPUT_HANDLER=]

Config options:
      --config-file <PATH>
          Config file [default: workspace-root/.config/nextest.toml]

      --tool-config-file <TOOL:ABS_PATH>
          Tool-specific config files.
          
          Some tools on top of nextest may want to set up their own default configuration but
          prioritize user configuration on top. Use this argument to insert configuration that's
          lower than --config-file in priority but above the default config shipped with nextest.
          
          Arguments are specified in the format "tool:abs_path", for example
          "my-tool:/path/to/nextest.toml" (or "my-tool:C:\path\to\nextest.toml" on Windows). Paths
          must be absolute.
          
          This argument may be specified multiple times. Files that come later are lower priority
          than those that come earlier.

      --override-version-check
          Override checks for the minimum version defined in nextest's config.
          
          Repository and tool-specific configuration files can specify minimum required and
          recommended versions of nextest. This option overrides those checks.

  -P, --profile <PROFILE>
          The nextest profile to use.
          
          Nextest's configuration supports multiple profiles, which can be used to set up different
          configurations for different purposes. (For example, a configuration for local runs and
          one for CI.) This option selects the profile to use.

          [env: NEXTEST_PROFILE=]