You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/src/book/how-it-works.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,4 +27,4 @@ A cargo-nextest run has two separate phases:
27
27
***The list phase.** cargo-nextest first builds all test binaries with `cargo test --no-run`, then queries those binaries to produce a list of all tests within them.
28
28
***The run phase.** cargo-nextest then executes each individual test in a separate process, in parallel. It then collects, displays and aggregates results for each individual test.
29
29
30
-
This model solves all the problems of cargo test's execution model, at the cost of a *significantly* thicker interface to test binaries. **This means that custom test harnesses [may need to be adapted](custom-test-harnesses.md) to work with cargo-nextest.**
30
+
This model solves all the problems of cargo test's execution model, at the cost of a *significantly* thicker interface to test binaries. This means that **custom test harnesses [may need to be adapted](custom-test-harnesses.md) to work with cargo-nextest.**
0 commit comments