ci: use nextest for test suites - #150
Merged
Merged
Conversation
✅ Deploy Preview for dryoc-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
brndnmtthws
marked this pull request as ready for review
July 22, 2026 12:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Use cargo-nextest for executable test suites in the build and publish workflows.
User Impact
CI and release validation now use the same faster test runner consistently across native, feature-matrix, MSRV, nightly, and WebAssembly jobs. Doctest coverage remains unchanged.
Root Cause
Several workflow jobs still invoked cargo test directly and did not install cargo-nextest, leaving test execution inconsistent across CI.
Fix
Install cargo-nextest with authenticated GitHub requests in each affected job and replace executable cargo test runs with cargo nextest run. Keep cargo test --doc because nextest does not support doctests.
Validation