Skip to content

Commit 84068cf

Browse files
authored
Tune down recommendation and point to bolero (rust-lang#2212)
I don't think we should discourage people from looking into Kani so I'm changing the words here. I also changed the reference to point to bolero instead of proptest.
1 parent 9439a54 commit 84068cf

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/src/application.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,8 @@ You may be interested in applying Kani if you're in this situation:
66
2. You've already invested heavily in testing to ensure correctness.
77
3. You want to invest further, to gain a much higher degree of assurance.
88

9-
> If you haven't already, we recommend techniques like property testing (e.g. with [`proptest`](https://github.com/AltSysrq/proptest)) before attempting model checking.
10-
> These yield good results, are very cheap to apply, and are often easier to adopt and debug.
11-
> Kani is a next step: a tool that can be applied once cheaper tactics are no longer yielding results, or once the easier to detect issues have already been dealt with.
9+
> If you haven't already, we also recommend techniques like property testing and fuzzing (e.g. with [`bolero`](https://github.com/camshaft/bolero/)).
10+
> These yield good results, are very cheap to apply, and are often easy to adopt and debug.
1211
1312
In this section, we explain [how Kani compares with other tools](./tool-comparison.md)
1413
and suggest [where to start applying Kani in real code](./tutorial-real-code.md).

0 commit comments

Comments
 (0)