nextest-scripts

Create a `.config/nextest.toml` file in your project and define wrapper commands (valgrind, heaptrack, perf, lldb, or custom tools) that wrap test binaries. Configure profiles to apply these wrappers to specific test runs using `cargo nextest run --profile <profile-name>`, enabling memory profiling, tracing, and resource limit instrumentation across Linux, macOS, and Windows.

Yes, setup scripts in nextest configuration run pre-test preparation steps including fixture creation, service startup, and environment initialization. Define these in your profile configuration to execute automatically before test execution, streamlining environment prep across different CI and local contexts.

Nextest wrapper infrastructure supports platform filters in TOML configurations, allowing you to define OS-specific wrapper commands and setup scripts for Linux, macOS, and Windows. Environment variables propagate to tests, enabling controlled cross-platform test execution with tailored instrumentation per platform.

Define multiple profiles in `.config/nextest.toml` with distinct wrapper and setup configurations for each context. Use profile-based run and list wrappers to activate different instrumentation, resource limits, or environment setups when running `cargo nextest run --profile <profile-name>`, automating CI-specific versus development-specific test execution.

Supported wrappers include valgrind for memory checking, heaptrack for heap profiling, strace for system call tracing, perf for performance profiling, and lldb for debugging, plus custom wrapper commands. Each wraps test binaries to enable controlled instrumentation, resource limits, or debugging across your test suite.

Yes, nextest-scripts is designed for projects requiring memory profiling, tracing, resource limits, or custom test environments. TOML-based configurations attach wrappers like valgrind and heaptrack and define setup steps, satisfying functional requirements for instrumented test runs with controlled resource allocation.