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
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.
Copy file name to clipboardExpand all lines: docs/src/application.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,8 @@ You may be interested in applying Kani if you're in this situation:
6
6
2. You've already invested heavily in testing to ensure correctness.
7
7
3. You want to invest further, to gain a much higher degree of assurance.
8
8
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.
12
11
13
12
In this section, we explain [how Kani compares with other tools](./tool-comparison.md)
14
13
and suggest [where to start applying Kani in real code](./tutorial-real-code.md).
0 commit comments