# cargo-nextest mit Homebrew, apk, Nix, pacman, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cargo-nextest in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:cargo-nextest
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install cargo-nextest
```

  Evidenz: local Homebrew formula metadata

### Linux

- apk (92%):

```sh
sudo apk add cargo-nextest
```

  Evidenz: Alpine Linux edge package indexes: cargo-nextest from https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz

- Nix (92%):

```sh
nix profile install nixpkgs#cargo-nextest
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/ca/cargo-nextest/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S cargo-nextest
```

  Evidenz: Arch Linux sync databases: cargo-nextest from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

### Windows

- winget (92%):

```sh
winget install --id nextest.cargo-nextest -e
```

  Evidenz: Windows Package Manager source index: nextest.cargo-nextest from https://cdn.winget.microsoft.com/cache/source.msix

## Paketfakten

- **Paketschlüssel:** brew:cargo-nextest
- **Paketmanager:** Homebrew
- **Version:** 0.9.140
- **Quellzusammenfassung:** Next-generation test runner for Rust
- **Homepage:** <https://nexte.st>
- **Repository:** <https://github.com/nextest-rs/nextest>
- **Zuletzt aktualisiert:** 2026-07-05T23:45:03Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- cargo-nextest (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.9.140
## Projektgeschichte und Nutzung

cargo-nextest is the cargo-facing binary for Nextest, a next-generation Rust test runner. The official repository README describes cargo-nextest as a newer, faster Cargo test runner and points users to nexte.st for documentation.

### Projektgeschichte

The cargo-nextest crate first appeared on crates.io in February 2022 as version 0.9.0. The repository README says the project is derived from diem-devtools, while the documentation positions it as a replacement runner for Rust test workflows.

### Adoptionsgeschichte

cargo-nextest has broad package-manager reach in the input facts: apk, Homebrew, Nix, Arch, and winget. Crates.io reported 11,087,886 downloads when checked on 2026-06-30, reflecting heavy use in Rust CI and local test loops.

### Wie es verwendet wird

Users run cargo nextest run to execute tests, configure repository behavior in .config/nextest.toml, and optionally use user config for personal UI preferences. The docs cover profiles, retries, timeouts, test groups, per-test overrides, archives, and integrations.

### Warum Paket-Nerds sich dafür interessieren

It is significant because it rethinks the default cargo test experience around fast execution, structured configuration, CI behavior, and machine-readable metadata, making test running a first-class package workflow rather than a fixed Cargo subcommand behavior.

### Zeitleiste

- 2022: First crates.io release 0.9.0.
- 2026: Crates.io latest version 0.9.138 and Homebrew stable version 0.9.138.

### Related projects

- Related projects include Cargo's built-in test runner, nextest-runner, nextest-metadata, nextest-filtering, cargo-llvm-cov integration, and the earlier diem-devtools codebase.

### Quellen

- <https://api.github.com/repos/nextest-rs/nextest>
- <https://github.com/nextest-rs/nextest>
- <https://nexte.st/docs>
- <https://crates.io/api/v1/crates/cargo-nextest>
- <https://formulae.brew.sh/api/formula/cargo-nextest.json>


## Sicherheitshinweise

Für cargo-nextest wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .config/nextest.toml, $XDG_CONFIG_HOME/nextest/config.toml, ~/.config/nextest/config.toml
- Windows: .config\nextest.toml, %APPDATA%\nextest\config.toml, %XDG_CONFIG_HOME%\nextest\config.toml, %HOME%\.config\nextest\config.toml
## Andere Paketmanager-Einträge

- Nix - cargo-nextest: normalized package name match | nixpkgs package indexes: pkgs/by-name/ca/cargo-nextest/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - cargo-nextest - 0.9.110-r0: normalized package name match | Alpine Linux edge package indexes: cargo-nextest from https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz | A next-generation test runner for Rust | https://nexte.st/
- pacman - cargo-nextest - 0.9.140-1: normalized package name match | Arch Linux sync databases: cargo-nextest from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A next-generation test runner for Rust. | https://github.com/nextest-rs/nextest
- winget - nextest.cargo-nextest: normalized package name match | Windows Package Manager source index: nextest.cargo-nextest from https://cdn.winget.microsoft.com/cache/source.msix


## Verwandte Links

- [cargo-nextest](https://pkg.so/de/pkg/cargo/cargo-nextest/) - Same normalized package name exists in another local package ecosystem.

## Combined YAML source

View the package source record on GitHub. [combined/cargo-nextest.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cargo-nextest.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
