nextest

Configure and execute Rust test runs with profiles, filters, retries, and JUnit reporting.

3|Updated Jan 10, 2026

Search Tags:#testing #rust #archiving #filters #ci #retries #nextest

Ready to run

npx skills add https://github.com/yankeeinlondon/rusty-biscuit --skill nextest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nextest
Source: https://github.com/yankeeinlondon/rusty-biscuit/tree/main/.claude/skills/nextest
Command: npx skills add https://github.com/yankeeinlondon/rusty-biscuit --skill nextest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run and optimize tests in large Rust workspaces to be faster and more reliable than cargo test.

Core Features & Use Cases

Run tests across multiple crates concurrently with fine-grained control via profiles and filters.
Support retries for flaky tests, timeouts, and test partitioning for CI sharding.
Generate CI-friendly output (JUnit) and enable archiving of build artifacts for faster pipelines.

Quick Start

Configure a minimal nextest workflow and run tests in CI with cargo nextest run --profile ci.

Frequently Asked Questions about nextest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run Rust tests faster in large workspaces?▼

To retry flaky Rust tests, nextest provides built-in retry configurations within its test profiles. You can define retry counts and timeouts to automatically re-run failed tests, improving reliability in both local development and CI pipelines.

How do I partition Rust tests for CI sharding?▼

To generate JUnit reports for Rust tests, nextest can output CI-friendly JUnit XML files using the --profile ci flag. This integration provides structured test results that CI platforms can parse for detailed failure tracking.

Can I archive Rust build artifacts to speed up CI pipelines?▼

To filter specific Rust tests, nextest allows fine-grained test selection through command-line filters. You can target specific crates, modules, or test names, enabling rapid iteration by running only the tests relevant to your current changes.

What is the best way to handle flaky tests in Rust CI?▼

Nextest differs from cargo test by offering advanced orchestration features like concurrent multi-crate execution, test partitioning for sharding, JUnit reporting, and build archiving. It is designed to be faster and more reliable for large Rust workspaces.